Move the wl1251 part of the wl12xx platform data structure into a new
structure specifically for wl1251. Change the platform data built-in
block and board files accordingly.
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Luciano Coelho coe...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c | 36 +--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ti/wlcore/sdio.c
b/drivers/net/wireless/ti/wlcore/sdio.c
.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/net/wireless/ti/wl12xx/main.c | 20 +---
drivers/net/wireless/ti/wlcore/sdio.c | 4
2 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ti/wl12xx
these internal clocks, so make the clock consumer
code generic enough. If external clocks are used, then the internal
clock device tree nodes are not necessary, but the external ones must
be specified.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers
support
for wl12xx when booted with devicetree), since this is not be needed
anymore, now that DT support for WiLink is implemented.
Cc: Tony Lindgren t...@atomide.com
Cc: Sekhar Nori nsek...@ti.com
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach
workaround to get WiLink to work on Panda while DT
was not supported yet.
Please review.
Luciano Coelho (8):
wl1251: split wl251 platform data to a separate structure
wlcore: set irq_flags in the board files instead of hiding behind a
quirk
wlcore: remove pwr_in_suspend from platform
The pwr_in_suspend flag depends on the MMC settings which can be
retrieved from the SDIO subsystem, so it doesn't need to be part of
the platform data structure. Move it to the platform device data that
is passed from SDIO to wlcore.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed
-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Acked-by: Sekhar Nori nsek...@ti.com
---
arch/arm/mach-davinci/board-da850-evm.c | 8 +++-
arch/arm/mach-omap2/board-omap3evm.c | 19 ++
arch/arm/mach-omap2/board-zoom-peripherals.c | 30
If platform data is not available, try to get the required information
from the device tree. Register an OF match table and parse the
appropriate device tree nodes.
Parse interrupt property only, for now.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
Add regulator, pin muxing and MMC5 configuration to be used by the
on-board WiLink6 module.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch
Add the WiLink device tree nodes. On omap4-panda, a WiLink6 module is
connected on MMC5 and a GPIO interrupt is used. The refclock
frequency is 38.4MHz.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 14 ++
1 file changed, 14 insertions
with clocks and SDIO stuff. So it's pretty much just
compiled tested. I've tried this (without the new clock definition
stuff) on Blaze with 3.10 and it was working, though.
Please take a look and let me know what you think.
Luca.
Luciano Coelho (4):
ARM: dts: omap4-panda: add MMC5 (WiLink WLAN
Add appropriate device tree node for Blaze's WiLink7 module. It uses
a GPIO as interrupt, so configure the gpio2 node as interrupt parent
and assign the corresponding GPIO. Additionally, add the clock
frequencies used by the module.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot
(using the new devicetree mailing list address)
On Tue, 2013-07-30 at 20:24 +0200, Laurent Pinchart wrote:
Hi Luciano,
Thank you for the patch.
On Monday 29 July 2013 17:55:28 Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
In v3, use IRQ_TYPE_LEVEL_HIGH in the example, as suggested by Laurent.
.../devicetree
think.
Luca.
Luciano Coelho (4):
ARM: dts: omap4-panda: add MMC5 (WiLink WLAN) configuration
arm: dts: omap4-panda-common: add WiLink6 device tree nodes
ARM: dts: omap4-sdp: add MMC5 (WiLink WLAN) configuration
arm: dts: omap4-sdp: add WiLink7 device tree node
arch/arm/boot/dts/omap4
Add regulator, pin muxing and MMC5 configuration to be used by the
on-board WiLink6 module.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot
Add appropriate device tree node for Blaze's WiLink7 module. It uses
a GPIO as interrupt, so configure the gpio2 node as interrupt parent
and assign the corresponding GPIO. Additionally, add the clock
frequencies used by the module.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot
Add regulator, pin muxing and MMC5 configuration to be used by the
on-board WiLink6 module.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot/dts/omap4-sdp.dts | 29 +
1 file changed, 29 insertions(+)
diff --git a/arch/arm/boot/dts/omap4-sdp.dts b/arch
Add the WiLink device tree nodes. On omap4-panda, a WiLink6 module is
connected on MMC5 and a GPIO interrupt is used. The refclock
frequency is 38.4MHz.
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 15 +++
1 file changed, 15 insertions
On Tue, 2013-07-30 at 15:35 -0700, Mike Turquette wrote:
Quoting Luciano Coelho (2013-07-30 06:04:34)
+static const struct of_device_id wlcore_sdio_of_clk_match_table[] = {
+ { .compatible = ti,wilink-clock },
+};
+
static struct wl12xx_platform_data *wlcore_get_pdata_from_of
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
Changes in v2:
Use generic clock definitions to get the clock data instead of passing
On Thu, 2013-07-18 at 01:59 -0700, Tony Lindgren wrote:
* Arend van Spriel ar...@broadcom.com [130718 01:47]:
Then for the SDIO with device tree, take a look at the following
patches:
[PATCH 0/3] WLAN support for omap4 when booted with devicetree
On Thu, 2013-07-18 at 01:58 +0200, Laurent Pinchart wrote:
Hi Luciano,
Hi Laurent,
On Monday 01 July 2013 15:39:30 Luciano Coelho wrote:
The only thing I can come up with is to make a small clock driver (maybe
even inside the WiLink module itself) that registers a new type of
clock, ti
On Wed, 2013-07-03 at 17:12 +0200, Javier Martinez Canillas wrote:
On Wed, Jul 3, 2013 at 4:15 PM, Luciano Coelho coe...@ti.com wrote:
On Wed, 2013-07-03 at 17:03 +0300, Luciano Coelho wrote:
The platform_quirk element in the platform data was used to change the
way the IRQ is triggered
On Wed, 2013-07-03 at 04:33 -0700, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130702 13:33]:
On Tue, 2013-07-02 at 10:02 -0500, Nishanth Menon wrote:
On 17:55-20130702, Luciano Coelho wrote:
Instead of defining an enumeration with the FW specific values for the
different
On Wed, 2013-07-03 at 13:13 +0300, Grazvydas Ignotas wrote:
Hi,
Hi Gražvydas,
On Tue, Jul 2, 2013 at 5:55 PM, Luciano Coelho coe...@ti.com wrote:
Hi,
This is a follow-up on a previous patch set that had a smaller
audience. This time, I added the lists and people who were involved
-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c | 36 +++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ti/wlcore/sdio.c
b/drivers/net/wireless/ti/wlcore/sdio.c
these internal clocks, so make the clock consumer
code generic enough. If external clocks are used, then the internal
clock device tree nodes are not necessary, but the external ones must
be specified.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers
...@ti.com
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/mach-davinci/board-da850-evm.c |3 +-
arch/arm/mach-omap2/board-4430sdp.c |5 ++-
arch/arm/mach-omap2/board-omap3evm.c |3 +-
arch/arm/mach-omap2/board-omap4panda.c |3 +-
arch/arm/mach-omap2
.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wl12xx/main.c | 20 +---
drivers/net/wireless/ti/wlcore/sdio.c |4
2 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ti/wl12xx/main.c
b/drivers/net/wireless/ti
requests (thanks Tony and Nishant).
Please review.
--
Cheers,
Luca.
Luciano Coelho (8):
wl1251: split wl251 platform data to a separate structure
wlcore: set irq_flags in the board files instead of hiding behind a
quirk
wlcore: remove pwr_in_suspend from platform data
wl12xx: use
If platform data is not available, try to get the required information
from the device tree. Register an OF match table and parse the
appropriate device tree nodes.
Parse interrupt property only, for now.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c
Move the wl1251 part of the wl12xx platform data structure into a new
structure specifically for wl1251. Change the platform data built-in
block and board files accordingly.
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Luciano Coelho coe...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
The pwr_in_suspend flag depends on the MMC settings which can be
retrieved from the SDIO subsystem, so it doesn't need to be part of
the platform data structure. Move it to the platform device data that
is passed from SDIO to wlcore.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net
-by: Luciano Coelho coe...@ti.com
---
arch/arm/mach-davinci/board-da850-evm.c |8 +-
arch/arm/mach-omap2/board-4430sdp.c | 18 +
arch/arm/mach-omap2/board-omap3evm.c | 19 ++
arch/arm/mach-omap2/board-omap4panda.c | 36
On Wed, 2013-07-03 at 17:03 +0300, Luciano Coelho wrote:
The platform_quirk element in the platform data was used to change the
way the IRQ is triggered. When set, the EDGE_IRQ quirk would change
the irqflags used and treat edge trigger differently from the rest.
Instead of hiding this irq
On Wed, 2013-07-03 at 17:13 +0300, Felipe Balbi wrote:
Hi,
On Wed, Jul 03, 2013 at 05:03:23PM +0300, Luciano Coelho wrote:
diff --git a/arch/arm/mach-omap2/board-4430sdp.c
b/arch/arm/mach-omap2/board-4430sdp.c
index 56a9a4f..953f620 100644
--- a/arch/arm/mach-omap2/board-4430sdp.c
these internal clocks, so make the clock consumer
code generic enough. If external clocks are used, then the internal
clock device tree nodes are not necessary, but the external ones must
be specified.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c |9
.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wl12xx/main.c | 20 +---
drivers/net/wireless/ti/wlcore/sdio.c |4
2 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/net/wireless/ti/wl12xx/main.c
b/drivers/net/wireless/ti
Read the clock nodes from the device tree and use them to set the
frequency for the refclock and the tcxo clock.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c | 36 +++--
1 file changed, 34 insertions(+), 2 deletions(-)
diff
Since we are now using threaded IRQs without the primary handler, we
need to set IRQF_ONESHOT, otherwise our request will fail.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wlcore/main.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers
If platform data is not available, try to get the required information
from the device tree. Register an OF match table and parse the
appropriate device tree nodes.
Parse interrupt property only, for now.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net/wireless/ti/wlcore/sdio.c
...@ti.com
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/mach-davinci/board-da850-evm.c |3 +-
arch/arm/mach-omap2/board-4430sdp.c |5 ++-
arch/arm/mach-omap2/board-omap3evm.c |3 +-
arch/arm/mach-omap2/board-omap4panda.c |3 +-
arch/arm/mach-omap2
Move the wl1251 part of the wl12xx platform data structure into a new
structure specifically for wl1251. Change the platform data built-in
block and board files accordingly.
Cc: Tony Lindgren t...@atomide.com
Signed-off-by: Luciano Coelho coe...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
);
* Patch 6/9 (previously patch 5/5) now doesn't add the clock parsing,
since it became more complicated and I added separate patches for
that;
* 3 new patches (from 7/9 till 9/9) to handle the clock reading in the
device tree;
Please review.
--
Cheers,
Luca.
Luciano Coelho (9):
wl1251
element and let the board file define what to use.
This will be more meaningful than driver-specific quirks when we
switch to DT.
Cc: Tony Lindgren t...@atomide.com
Cc: Sekhar Nori nsek...@ti.com
Signed-off-by: Luciano Coelho coe...@ti.com
Acked-by: Tony Lindgren t...@atomide.com
---
arch/arm/mach
The pwr_in_suspend flag depends on the MMC settings which can be
retrieved from the SDIO subsystem, so it doesn't need to be part of
the platform data structure. Move it to the platform device data that
is passed from SDIO to wlcore.
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/net
On Tue, 2013-07-02 at 18:26 +0300, Felipe Balbi wrote:
Hi,
On Tue, Jul 02, 2013 at 05:55:41PM +0300, Luciano Coelho wrote:
The platform_quirk element in the platform data was used to change the
way the IRQ is triggered. When set, the EDGE_IRQ quirk would change
the irqflags used
On Tue, 2013-07-02 at 18:31 +0300, Felipe Balbi wrote:
Hi,
On Tue, Jul 02, 2013 at 05:55:43PM +0300, Luciano Coelho wrote:
diff --git a/drivers/net/wireless/ti/wl12xx/main.c
b/drivers/net/wireless/ti/wl12xx/main.c
index 1c627da..903dcb3 100644
--- a/drivers/net/wireless/ti/wl12xx
On Tue, 2013-07-02 at 18:32 +0300, Felipe Balbi wrote:
On Tue, Jul 02, 2013 at 05:55:44PM +0300, Luciano Coelho wrote:
Since we are now using threaded IRQs without the primary handler, we
need to set IRQF_ONESHOT, otherwise our request will fail.
Signed-off-by: Luciano Coelho coe
On Tue, 2013-07-02 at 18:35 +0300, Felipe Balbi wrote:
Hi,
On Tue, Jul 02, 2013 at 05:55:47PM +0300, Luciano Coelho wrote:
@@ -294,6 +316,8 @@ static int wl1271_probe(struct sdio_func *func,
/* Use block mode for transferring over one block size of data */
func-card-quirks
On Tue, 2013-07-02 at 10:02 -0500, Nishanth Menon wrote:
On 17:55-20130702, Luciano Coelho wrote:
Instead of defining an enumeration with the FW specific values for the
different clock rates, use the actual frequency instead. Also add a
boolean to specify whether the clock is XTAL
On Wed, 2013-07-03 at 00:32 +0300, Felipe Balbi wrote:
On Tue, Jul 02, 2013 at 11:19:54PM +0300, Luciano Coelho wrote:
On Tue, 2013-07-02 at 18:35 +0300, Felipe Balbi wrote:
Hi,
On Tue, Jul 02, 2013 at 05:55:47PM +0300, Luciano Coelho wrote:
@@ -294,6 +316,8 @@ static int
On Fri, 2013-06-28 at 16:21 +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 15:18 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 03:13:52PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 14:41 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 02:22:11PM +0300, Luciano Coelho
these internal clocks, so make the clock consumer
code generic enough. If external clocks are used, then the internal
clock device tree nodes are not necessary, but the external ones must
be specified.
Signed-off-by: Luciano Coelho coe...@ti.com
---
Hi,
I came up with this code, trying to make
On Mon, 2013-07-01 at 23:46 +0300, Felipe Balbi wrote:
Hi,
On Mon, Jul 01, 2013 at 10:34:10PM +0300, Luciano Coelho wrote:
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot/dts/omap4-panda-common.dtsi
index 670c3ce..7f061b8 100644
--- a/arch/arm/boot/dts/omap4
On Fri, 2013-06-28 at 10:38 +0100, Mark Rutland wrote:
On Tue, Jun 25, 2013 at 09:35:30AM +0100, Luciano Coelho wrote:
+Optional properties:
+
+
+- refclock: the internal WLAN reference clock frequency (required for
+ WiLink6 and WiLink7; not used for WiLink8
(fixed Mike's address)
On Fri, 2013-06-28 at 11:21 +0100, Mark Rutland wrote:
On Fri, Jun 28, 2013 at 10:53:35AM +0100, Luciano Coelho wrote:
On Fri, 2013-06-28 at 10:38 +0100, Mark Rutland wrote:
On Tue, Jun 25, 2013 at 09:35:30AM +0100, Luciano Coelho wrote:
+Optional properties
On Fri, 2013-06-28 at 13:31 +0300, Luciano Coelho wrote:
(fixed Mike's address)
On Fri, 2013-06-28 at 11:21 +0100, Mark Rutland wrote:
On Fri, Jun 28, 2013 at 10:53:35AM +0100, Luciano Coelho wrote:
On Fri, 2013-06-28 at 10:38 +0100, Mark Rutland wrote:
On Tue, Jun 25, 2013 at 09:35
On Fri, 2013-06-28 at 14:41 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 02:22:11PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 13:31 +0300, Luciano Coelho wrote:
(fixed Mike's address)
On Fri, 2013-06-28 at 11:21 +0100, Mark Rutland wrote:
On Fri, Jun 28, 2013 at 10
On Fri, 2013-06-28 at 15:18 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 03:13:52PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 14:41 +0300, Felipe Balbi wrote:
On Fri, Jun 28, 2013 at 02:22:11PM +0300, Luciano Coelho wrote:
On Fri, 2013-06-28 at 13:31 +0300, Luciano Coelho
(added mailing lists and everyone back to the thread)
On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote:
On 06/25/2013 03:35 AM, Luciano Coelho wrote:
+Optional properties:
+
+
+- refclock: the internal WLAN reference clock frequency (required for
+ WiLink6
On Thu, 2013-06-27 at 07:51 -0500, Nishanth Menon wrote:
On 11:47-20130627, Luciano Coelho wrote:
(added mailing lists and everyone back to the thread)
On Wed, 2013-06-26 at 23:38 -0500, Nishanth Menon wrote:
On 06/25/2013 03:35 AM, Luciano Coelho wrote:
+Optional properties
On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com wrote:
For the actual DTS files, I could add a wilink.dtsi with enumerations
for these values so they could be used in the node definitions. But I'm
not sure it's going
On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote:
On 06/27/2013 08:19 AM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 7:58 AM, Luciano Coelho coe...@ti.com wrote:
For the actual DTS files, I could add a wilink.dtsi
On Thu, 2013-06-27 at 08:39 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote:
On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote:
On 06/27/2013 08:19 AM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:15 -0500, Nishanth Menon wrote
On Thu, 2013-06-27 at 14:12 -0500, Nishanth Menon wrote:
On 06/27/2013 01:51 PM, Luciano Coelho wrote:
On Thu, 2013-06-27 at 08:39 -0500, Nishanth Menon wrote:
On Thu, Jun 27, 2013 at 8:30 AM, Luciano Coelho coe...@ti.com wrote:
On Thu, 2013-06-27 at 08:23 -0500, Nishanth Menon wrote
Hi Tony,
On Tue, 2013-06-25 at 23:24 -0700, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130625 12:43]:
On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
---
I created a new directory under net to contain wireless bindings documentation.
The actual
On Tue, 2013-06-25 at 14:12 +0300, Felipe Balbi wrote:
On Tue, Jun 25, 2013 at 11:35:30AM +0300, Luciano Coelho wrote:
+- tcxoclock: the internal WLAN TCXO clock frequency (required for
+ WiLink7 not used for WiLink6 and WiLink8). Must be one of the
+ following:
+ 0 = 19.200 MHz
(fixed the ARM mailing list address)
On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano Coelho coe...@ti.com
(oh crap, now *really* fixed the ARM mailing list address)
On Tue, 2013-06-25 at 11:35 +0300, Luciano Coelho wrote:
Add device tree bindings documentation for the TI WiLink modules.
Currently only the WLAN part of the WiLink6, WiLink7 and WiLink8
modules is supported.
Signed-off-by: Luciano
In commit 3451c067 (mmc: omap: add DMA engine support), some #if 0's
were used to comment out parts of the code. This has been in the code
for over a year and are not needed anymore (and the commented-out code
doesn't even compile). Remove them.
Signed-off-by: Luciano Coelho coe...@ti.com
On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
Hi all,
Hi Tony,
Here are some patches against linux next to make WLAN to work with
device tree. Note that we still are initializing wl12xx with pdata,
but so far it looks like only minimal binding for it is needed.
Thanks for doing
On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
Without WLAN we cannot switch omap4 to use device tree
only booting. This patch can be reverted when the
binding for wl12xx is added.
Cc: Luciano Coelho coe...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Rajendra Nayak rna
provide a patch
for the missing GPIO muxes for blaze, see the the panda for
what's currently missing.
Cc: Luciano Coelho coe...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Rajendra Nayak rna...@ti.com
Cc: Ruslan Bilovol ruslan.bilo...@ti.com
Cc: devicetree-disc...@lists.ozlabs.org
Signed-off
down.
The PBIAS voltage is only available for the first controller
instance, so let's limit the PBIAS workaround to the first
controller only.
Signed-off-by: Tony Lindgren t...@atomide.com
---
Tested-by: Luciano Coelho coe...@ti.com
--
Luca.
--
To unsubscribe from this list: send
Hi Koen,
On Fri, 2013-04-26 at 11:33 +0200, Koen Kooi wrote:
Op 26 apr. 2013, om 05:52 heeft Tony Lindgren t...@atomide.com het volgende
geschreven:
Without WLAN we cannot switch omap4 to use device tree
only booting. This patch can be reverted when the
binding for wl12xx is added.
On Fri, 2013-04-26 at 14:00 +0300, Luciano Coelho wrote:
Hi Koen,
On Fri, 2013-04-26 at 11:33 +0200, Koen Kooi wrote:
Op 26 apr. 2013, om 05:52 heeft Tony Lindgren t...@atomide.com het
volgende geschreven:
Without WLAN we cannot switch omap4 to use device tree
only booting
instead of ti,non-removable
as the ti,non-removable also sets no_regulator_off_init which
is really not what we want as then wl12xx won't get powered
up and down which is needed for resetting it.
Cc: Luciano Coelho coe...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Rajendra Nayak rna
On Thu, 2013-01-31 at 16:42 -0500, Matt Porter wrote:
On Thu, Jan 31, 2013 at 08:58:39PM +, Arnd Bergmann wrote:
On Thursday 31 January 2013, Matt Porter wrote:
On Wed, Jan 30, 2013 at 09:32:58AM +, Arnd Bergmann wrote:
On Wednesday 30 January 2013, Matt Porter wrote:
+
On Wed, 2013-01-30 at 14:18 +0530, Santosh Shilimkar wrote:
On Wednesday 30 January 2013 02:13 PM, Kumar, Anil wrote:
Hi Sourav,
On Wed, Jan 30, 2013 at 12:10:18, Poddar, Sourav wrote:
Hi Luciano,
On Wednesday 30 January 2013 11:55 AM, Luciano Coelho wrote:
Hi Sourav,
On Mon, 2013
Hi Sourav,
On Mon, 2013-01-28 at 16:47 +0530, Sourav Poddar wrote:
Booting 3.8-rc4 om omap 4430sdp results in the following error
omap_i2c 4807.i2c: did not get pins for i2c error: -19
[1.024261] omap_i2c 4807.i2c: bus 0 rev0.12 at 100 kHz
[1.030181] omap_i2c 48072000.i2c:
when device tree support is
implemented.
Signed-off-by: Luciano Coelho coe...@ti.com
Reviewed-by: Felipe Balbi ba...@ti.com
---
In v2:
* Fix ti/Makefile
* Modify board_omap3evm.c which was still using the old Kconfig define
Tony, is it okay if I add this change in the omap3evm board
Add the UART2 muxing data to the board file (this used to be,
erroneously, done in the bootloader).
Cc: stable sta...@vger.kernel.org [3.7]
Signed-off-by: Luciano Coelho coe...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm
On Thu, 2013-01-17 at 15:16 -0800, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130117 10:04]:
But this patch is pretty small and simple, so why not include it to at
least fix the breakage in 3.7 and 3.8? Whether you take it or not now
won't make any difference in the 5k LOC
On Fri, 2013-01-18 at 09:36 -0800, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130118 01:03]:
On Thu, 2013-01-17 at 15:16 -0800, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130117 10:04]:
But this patch is pretty small and simple, so why not include it to at
least
On Thu, 2013-01-17 at 10:30 +0100, Peter Ujfalusi wrote:
Hi Luca,
Hi Péter!
On 01/16/2013 10:45 PM, Luciano Coelho wrote:
static struct ti_st_plat_data wilink_platform_data = {
- .nshutdown_gpio = 46,
.dev_name = /dev/ttyO1,
.flow_cntrl = 1,
.baud_rate
On Thu, 2013-01-17 at 12:09 +0200, Felipe Balbi wrote:
On Thu, Jan 17, 2013 at 12:05:10PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Jan 17, 2013 at 10:55:14AM +0100, Peter Ujfalusi wrote:
On 01/17/2013 10:34 AM, Felipe Balbi wrote:
I just wonder how this is going to work with DT... You
Hi Tony,
On Thu, 2013-01-17 at 09:31 -0800, Tony Lindgren wrote:
* Peter Ujfalusi peter.ujfal...@ti.com [130117 02:44]:
On 01/17/2013 11:35 AM, Luciano Coelho wrote:
This out-of-tree code doesn't explain why we need to do the
enable/disable in the board file. We just need to do things
-by: Luciano Coelho coe...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c | 57 +---
1 file changed, 53 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
b/arch/arm/mach-omap2/board-omap4panda.c
index 5c8e9ce..97a274b 100644
--- a/arch/arm
On Wed, 2013-01-16 at 19:10 -0200, Fabio Estevam wrote:
On Wed, Jan 16, 2013 at 6:34 PM, Luciano Coelho coe...@ti.com wrote:
+static int wilink_st_init(void)
+{
+ int status;
+
+ status = gpio_request(GPIO_BT_EN, kim);
+ if (status) {
+ pr_err(%s
...@vger.kernel.org [3.7]
Signed-off-by: Luciano Coelho coe...@ti.com
---
In v2: use gpio_request_one() instead of gpio_request() and
gpio_direction_output(). (Thanks Fabio!)
arch/arm/mach-omap2/board-omap4panda.c | 50 +---
1 file changed, 46 insertions(+), 4 deletions
Add the btwilink, nfcwilink and shared transport devices to the board
file, including functions to power things on and off.
Additionally, add the UART2 muxing data, so it's properly configured.
Signed-off-by: Luciano Coelho coe...@ti.com
---
This is pretty much the same as the patch I just sent
Hi Mark,
On Wed, 2012-12-19 at 09:45 +, Mark Brown wrote:
On Tue, Dec 18, 2012 at 11:54:50AM +0200, Felipe Balbi wrote:
damn, this is still part of our v3.7-rc kernel. Original commit was done
with no testing whatsoever and caused a big regression to (at least)
TI's WiFi driver which
On Wed, 2012-12-19 at 10:28 +, Mark Brown wrote:
On Wed, Dec 19, 2012 at 12:01:57PM +0200, Luciano Coelho wrote:
I think one of the reasons not many people use the mainline with TWL is
exactly because something seems to break on every new kernel release.
I'm one of those who care
On Wed, 2012-12-19 at 10:32 +, Mark Brown wrote:
On Wed, Dec 19, 2012 at 11:18:11AM +0100, Peter Ujfalusi wrote:
Sure. It must be a clock driver. I already have similar driver (for McPDM
fclk
clock) for twl6040.
Let me check linux-next, if CCF is there for OMAP I can send the 32k
On Wed, 2012-12-19 at 11:56 +0100, Peter Ujfalusi wrote:
On 12/19/2012 11:45 AM, Luciano Coelho wrote:
Well, we still haven't got the foggiest idea what the actual problem is
beyond that it's probably related to the 32kHz clock in some way (unless
it was one of the other reverts
On Wed, 2012-12-19 at 14:51 +0100, Benoit Cousson wrote:
On 12/19/2012 02:01 PM, Felipe Balbi wrote:
On Wed, Dec 19, 2012 at 11:56:20AM +0100, Peter Ujfalusi wrote:
BTW: have you happened to ubdate u-boot recently? There is a nice easter
egg
added there:
f3f98bb ARM: OMAP4/5: Do not
1 - 100 of 168 matches
Mail list logo
