Hi,
I'm working on a board derived from the DragonBoard-410c (apq8016 +
wcn3620) and noticed an issue with WiFi connection monitoring. When I
get out of the range of the access point, the device stays associated,
no matter how far I go or how long I wait.
The chip on this board is the WCN3620,
Hi Marc,
I tested the new technologic version and it works as expected. Would be
nice if someone could test the nxp version to ensure no regressions has
been introduced (I don't have such hardware here).
On Wed, Jan 20, 2016 at 04:43:31PM +0100, Marc Kleine-Budde wrote:
> From: Damien Rie
Hi Marc,
On Wed, Jan 20, 2016 at 11:23:49AM +0100, Marc Kleine-Budde wrote:
> From: Damien Riegel <damien.rie...@savoirfairelinux.com>
>
> This commit adds the capability to allocate and init private data
> embedded in the sja1000_priv structure on a per-compatible basis.
adds a new compatible device, "technologic,sja1000", with
read and write functions using the window mechanism.
Signed-off-by: Damien Riegel <damien.rie...@savoirfairelinux.com>
---
drivers/net/can/sja1000/sja1000_platform.c | 47 ++
1 file changed, 47 insertion
This commit adds the capability to allocate and init private data
embedded in the sja1000_priv structure on a per-compatible basis. The
device node is passed as a parameter of the init callback to allow
parsing of custom device tree properties.
Signed-off-by: Damien Riegel <damien.
,write}16
Damien Riegel (3):
can: sja1000: of: add per-compatible init hook
can: sja1000: add documentation for Technologic Systems version
can: sja1000: of: add compatibility with Technologic Systems version
.../devicetree/bindings/net/can/sja1000.txt| 3 +-
drivers/net/can/sja1000
This commit adds documentation for the Technologic Systems version of
SJA1000. The difference with the NXP version is in the way the registers
are accessed.
Signed-off-by: Damien Riegel <damien.rie...@savoirfairelinux.com>
---
Documentation/devicetree/bindings/net/can/sja1000.txt | 3 ++-
On Sat, Dec 19, 2015 at 09:37:42PM -0600, Rob Herring wrote:
> On Fri, Dec 18, 2015 at 03:17:24PM -0500, Damien Riegel wrote:
> > This commit adds documentation for the Technologic Systems version of
> > SJA1000. The difference with the NXP version is in the way the registers
&
This commit adds the capability to allocate and init private data
embedded in the sja1000_priv structure on a per-compatible basis. The
device node is passed as a parameter of the init callback to allow
parsing of custom device tree properties.
Signed-off-by: Damien Riegel <damien.
adds a new compatible device, "technologic,sja1000", with
read and write functions using the window mechanism.
Signed-off-by: Damien Riegel <damien.rie...@savoirfairelinux.com>
---
drivers/net/can/sja1000/sja1000_platform.c | 30 --
1 file changed, 28 insertion
This commit adds documentation for the Technologic Systems version of
SJA1000. The difference with the NXP version is in the way the registers
are accessed.
Signed-off-by: Damien Riegel <damien.rie...@savoirfairelinux.com>
---
Documentation/devicetree/bindings/net/can/sja1000.txt | 3 ++-
On Fri, Dec 18, 2015 at 09:41:47PM +0100, Marc Kleine-Budde wrote:
> On 12/18/2015 09:17 PM, Damien Riegel wrote:
> > Technologic Systems provides an IP compatible with the SJA1000,
> > instantiated in an FPGA. Because of some bus widths issue, access to
> > registers is m
12 matches
Mail list logo
