linux-stable.git/include/net/ieee802154_netdev.h, branch linux-3.19.y

ieee802154: remove mlme get_phy callback

2014-11-05T20:53:04+00:00

This patch removes the get_phy callback from mlme ops structure. Instead
we doing a dereference via ieee802154_ptr dev pointer. For backwards
compatibility we need to run get_device after dereference wpan_phy via
ieee802154_ptr.

Signed-off-by: Alexander Aring 
Signed-off-by: Marcel Holtmann

ieee802154: move ieee802154 header

2014-10-25T19:39:57+00:00

This patch moves the ieee802154 header into include/linux instead
include/net. Similar like wireless which have the ieee80211 header
inside of include/linux.

Signed-off-by: Alexander Aring 
Cc: Alan Ott 
Signed-off-by: Marcel Holtmann

ieee802154: mac802154: remove FSF address

2014-10-25T06:07:30+00:00

This patch removes the FSF address in files which belongs to ieee802154
and mac802154.

Signed-off-by: Alexander Aring 
Cc: Alan Ott 
Signed-off-by: Marcel Holtmann

ieee802154, mac802154: implement devkey record option

2014-05-16T21:23:42+00:00

The 802.15.4-2011 standard states that for each key, a list of devices
that use this key shall be kept. Previous patches have only considered
two options:

 * a device "uses" (or may use) all keys, rendering the list useless
 * a device is restricted to a certain set of keys

Another option would be that a device *may* use all keys, but need not
do so, and we are interested in the actual set of keys the device uses.
Recording keys used by any given device may have a noticable performance
impact and might not be needed as often. The common case, in which a
device will not switch keys too often, should still perform well.

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

mac802154: add llsec configuration functions

2014-05-16T21:23:41+00:00

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

mac802154: integrate llsec with wpan devices

2014-05-16T21:23:41+00:00

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

ieee802154: add types for link-layer security

2014-05-16T21:23:40+00:00

The added structures match 802.15.4-2011 link-layer security PIBs as
closely as is reasonable. Some lists required by the standard were
modeled as bitmaps (frame_types and command_frame_ids in *llsec_key,
802.15.4-2011 7.5/Table 61), since using lists for those seems a bit
excessive and not particularly useful. The DeviceDescriptorHandleList
was inverted and is here a per-device list, since operations on this
list are likely to have both a key and a device at hand, and per-device
lists of keys are shorter than per-key lists of devices.

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

ieee802154: change _cb handling slightly

2014-05-15T19:51:42+00:00

The current mac_cb handling of ieee802154 is rather awkward and limited.
Decompose the single flags field into multiple fields with the meanings
of each subfield of the flags field to make future extensions (for
example, link-layer security) easier. Also don't set the frame sequence
number in upper layers, since that's a thing the MAC is supposed to set
on frame transmit - we set it on header creation, but assuming that
upper layers do not blindly duplicate our headers, this is fine.

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

ieee802154: add definitions for link-layer security and header functions

2014-05-15T19:51:42+00:00

When dealing with 802.15.4, one often has to know the maximum payload
size for a given packet. This depends on many factors, one of which is
whether or not a security header is present in the frame. These
definitions and functions provide an easy way for any upper layer to
calculate the maximum payload size for a packet. The first obvious user
for this is 6lowpan, which duplicates this calculation and gets it
partially wrong because it ignores security headers.

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller

mac802154: make csma/cca parameters per-wpan

2014-04-01T20:25:51+00:00

Commit 9b2777d6089bcd (ieee802154: add TX power control to wpan_phy)
and following erroneously added CSMA and CCA parameters for 802.15.4
devices as PHY parameters, while they are actually MAC parameters and
can differ for any two WPAN instances. Since it is now sensible to have
multiple WPAN devices with differing CSMA/CCA parameters, make these
parameters MAC parameters instead.

Signed-off-by: Phoebe Buckheister 
Signed-off-by: David S. Miller