BIT_TXNIE | BIT_TXNIE, BIT_TXNIE | BIT_TXNIE);
+ BIT_TXNIE | BIT_RXIE, BIT_TXNIE | BIT_RXIE);
}
static int mrf24j40_set_channel(struct ieee802154_hw *hw, u8 page, u8 channel)
Could you review this and give me your ack when you are happy so I can apply it
to my tree?
A
ret = -EINVAL;
+ goto err_register_device;
}
ret = mrf24j40_hw_init(devrec);
Acked-by: Alan Ott
On 02/18/2016 01:34 PM, zopieux wrote:
Fix the MRF24J40 handling of security-enabled frames so it does not
block upon receiving such frames.
Signed-off-by: Alexander Aring
Reported-by: Alexandre Macabies
Tested-by: Alexandre Macabies
---
When receiving a security-enabled IEEE 802.15.4 frame,
On 02/23/2016 04:29 AM, Alexander Aring wrote:
Alan, do you have some comments about that?
Currently the mrf24j40 goes into a deadlock if a frame with security
enable bit is set. As you see, I helped myself to create this patch and solve
this stupid default behaviour of mrf24j40. :-)
Hi Alex,
On 06/23/2015 10:52 AM, Antonio Borneo wrote:
In ancient times it was necessary to manually initialize the bus
field of an spi_driver to spi_bus_type. These days this is done in
spi_register_driver(), so we can drop the manual assignment.
Signed-off-by: Antonio Borneo
To: Alan Ott
To
