(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:
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
> > + followin
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
---
I created a new directory under net to contain wireless bindings documentation.
The actual implementation
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
On Mon, 2013-05-20 at 21:52 +0200, Peter Huewe wrote:
> Removing some boilerplate by using module_spi_driver instead of calling
> register and unregister in the otherwise empty init/exit functions
>
> Signed-off-by: Peter Huewe
> ---
Applied. Thanks, Peter.
--
Luca.
--
To unsubscribe from
On Mon, 2013-05-20 at 21:52 +0200, Peter Huewe wrote:
Removing some boilerplate by using module_spi_driver instead of calling
register and unregister in the otherwise empty init/exit functions
Signed-off-by: Peter Huewe peterhu...@gmx.de
---
Applied. Thanks, Peter.
--
Luca.
--
To
On Thu, 2013-02-28 at 15:51 +0800, Li Fei wrote:
> Even in failed case of pm_runtime_get_sync, the usage_count
> is incremented. In order to keep the usage_count with correct
> value and runtime power management to behave correctly, call
> pm_runtime_put(_sync) in such case.
>
> Signed-off-by Liu
On Thu, 2013-02-28 at 15:51 +0800, Li Fei wrote:
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync) in such case.
Signed-off-by Liu
On Thu, 2013-02-28 at 15:51 +0800, Li Fei wrote:
> Even in failed case of pm_runtime_get_sync, the usage_count
> is incremented. In order to keep the usage_count with correct
> value and runtime power management to behave correctly, call
> pm_runtime_put(_sync) in such case.
>
> Signed-off-by Liu
On Thu, 2013-02-28 at 15:51 +0800, Li Fei wrote:
Even in failed case of pm_runtime_get_sync, the usage_count
is incremented. In order to keep the usage_count with correct
value and runtime power management to behave correctly, call
pm_runtime_put(_sync) in such case.
Signed-off-by Liu
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore: remove if_ops from platform_data)
reintroduced a couple of those. This patch removes them.
Signed-off-by: Luciano Coelho
On Mon, 2013-02-11 at 00:07 -0800, Joe Perches wrote:
> On Mon, 2013-02-11 at 10:02 +0200, Luciano Coelho wrote:
> > In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
> > alloc cleanups) OOM messages after alloc were removed from the wlcore
> > modules.
>
On Mon, 2013-02-11 at 10:02 +0200, Luciano Coelho wrote:
> In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
> alloc cleanups) OOM messages after alloc were removed from the wlcore
> modules.
>
> Commit afb43e6d (wlcore: remove if_ops from platform_data)
> rei
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore: remove if_ops from platform_data)
reintroduced a couple of those. This patch removes them.
Signed-off-by: Luciano Coelho
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore: remove if_ops from platform_data)
reintroduced a couple of those. This patch removes them.
Signed-off-by: Luciano Coelho
On Mon, 2013-02-11 at 10:02 +0200, Luciano Coelho wrote:
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore: remove if_ops from platform_data)
reintroduced a couple
On Mon, 2013-02-11 at 00:07 -0800, Joe Perches wrote:
On Mon, 2013-02-11 at 10:02 +0200, Luciano Coelho wrote:
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore
In commit 0d2e7a5c (wireless: Remove unnecessary alloc/OOM messages,
alloc cleanups) OOM messages after alloc were removed from the wlcore
modules.
Commit afb43e6d (wlcore: remove if_ops from platform_data)
reintroduced a couple of those. This patch removes them.
Signed-off-by: Luciano Coelho
On Mon, 2013-02-11 at 18:40 +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 11 Feb 2013 08:47:54 +0200 Luciano Coelho wrote:
> >
> > On Sun, 2013-02-10 at 18:58 -0800, Joe Perches wrote:
> > > On Mon, 2013-02-11 at 13:33 +1100, Stephen Rothwell wrote:
>
On Sun, 2013-02-10 at 18:58 -0800, Joe Perches wrote:
> On Mon, 2013-02-11 at 13:33 +1100, Stephen Rothwell wrote:
> > Hi John,
> >
> > Today's linux-next merge of the wireless-next tree got conflicts in
> > drivers/net/wireless/ti/wlcore/sdio.c and
> > drivers/net/wireless/ti/wlcore/spi.c
On Sun, 2013-02-10 at 18:58 -0800, Joe Perches wrote:
On Mon, 2013-02-11 at 13:33 +1100, Stephen Rothwell wrote:
Hi John,
Today's linux-next merge of the wireless-next tree got conflicts in
drivers/net/wireless/ti/wlcore/sdio.c and
drivers/net/wireless/ti/wlcore/spi.c between commit
On Mon, 2013-02-11 at 18:40 +1100, Stephen Rothwell wrote:
Hi all,
On Mon, 11 Feb 2013 08:47:54 +0200 Luciano Coelho coe...@ti.com wrote:
On Sun, 2013-02-10 at 18:58 -0800, Joe Perches wrote:
On Mon, 2013-02-11 at 13:33 +1100, Stephen Rothwell wrote:
Today's linux-next merge
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 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
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
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
Reviewed-by: Felipe Balbi
---
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 in this
patch and queue it via
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
On Wed, 2013-01-23 at 10:21 +0100, Peter Ujfalusi wrote:
> On 01/23/2013 10:14 AM, Luciano Coelho wrote:
> > Yes, most likely we can use usleep or something. I'll look into that as
> > part of my clean-up series. ;)
>
> I would suggest to use usleep_range() instead of usle
On Wed, 2013-01-23 at 10:05 +0100, Peter Ujfalusi wrote:
> On 01/23/2013 10:04 AM, Peter Ujfalusi wrote:
> > On 01/22/2013 10:31 PM, Luciano Coelho wrote:
> >> I thought about checking exactly what we need as delays and whether we
> >> really need to do all that togglin
On Wed, 2013-01-23 at 10:05 +0100, Peter Ujfalusi wrote:
On 01/23/2013 10:04 AM, Peter Ujfalusi wrote:
On 01/22/2013 10:31 PM, Luciano Coelho wrote:
I thought about checking exactly what we need as delays and whether we
really need to do all that toggling. At least in some boards
On Wed, 2013-01-23 at 10:21 +0100, Peter Ujfalusi wrote:
On 01/23/2013 10:14 AM, Luciano Coelho wrote:
Yes, most likely we can use usleep or something. I'll look into that as
part of my clean-up series. ;)
I would suggest to use usleep_range() instead of usleep() if you can.
Yes
On Tue, 2013-01-22 at 12:14 -0800, Tony Lindgren wrote:
> * Luciano Coelho [130121 03:16]:
> > This reverts commit eccf2979b2c034b516e01b8a104c3739f7ef07d1.
> >
> > The reason is that it broke TI WiLink shared transport on Panda.
> > Also, callback functions should
On Tue, 2013-01-22 at 12:14 -0800, Tony Lindgren wrote:
* Luciano Coelho coe...@ti.com [130121 03:16]:
This reverts commit eccf2979b2c034b516e01b8a104c3739f7ef07d1.
The reason is that it broke TI WiLink shared transport on Panda.
Also, callback functions should not be added to board
Add the UART2 muxing data to the board file (this used to be,
erroneously, done in the bootloader).
Cc: stable [3.7]
Signed-off-by: Luciano Coelho
---
arch/arm/mach-omap2/board-omap4panda.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/mach-omap2/board-omap4panda.c
b
name ('status' to 'err') so that this
revert compiles properly.
Cc: stable [3.7]
Signed-off-by: Luciano Coelho
---
drivers/misc/ti-st/st_kim.c | 37 -
1 file changed, 36 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/ti-st/st_kim.c b/drivers/misc
name ('status' to 'err') so that this
revert compiles properly.
Cc: stable sta...@vger.kernel.org [3.7]
Signed-off-by: Luciano Coelho coe...@ti.com
---
drivers/misc/ti-st/st_kim.c | 37 -
1 file changed, 36 insertions(+), 1 deletion(-)
diff --git a/drivers
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 Fri, 2013-01-18 at 09:36 -0800, Tony Lindgren wrote:
> * Luciano Coelho [130118 01:03]:
> > On Thu, 2013-01-17 at 15:16 -0800, Tony Lindgren wrote:
> > > * Luciano Coelho [130117 10:04]:
> > > > But this patch is pretty small and simple, so why not incl
On Thu, 2013-01-17 at 15:16 -0800, Tony Lindgren wrote:
> * Luciano Coelho [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 dif
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
Hi Tony,
On Thu, 2013-01-17 at 09:31 -0800, Tony Lindgren wrote:
> * Peter Ujfalusi [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 j
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
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&
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
n Kconfigs.
>
> Cc: Luciano Coelho
> Cc: "John W. Linville"
> Cc: "David S. Miller"
> Cc: Greg Kroah-Hartman
> Signed-off-by: Kees Cook
> ---
> drivers/net/wireless/ti/wl1251/Kconfig |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
&
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
---
This is pretty much the same as the patch I just sent for panda
]
Signed-off-by: Luciano Coelho
---
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(-)
diff --git a/arch/arm/mach-omap2
On Wed, 2013-01-16 at 19:10 -0200, Fabio Estevam wrote:
> On Wed, Jan 16, 2013 at 6:34 PM, Luciano Coelho wrote:
>
> > +static int wilink_st_init(void)
> > +{
> > + int status;
> > +
> > + status = gpio_request(GPIO_BT_EN, "kim");
> &
-by: Luciano Coelho
---
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/mach-omap2/board
On Wed, 2013-01-16 at 11:43 +0800, Ming Lei wrote:
> On Tue, Jan 15, 2013 at 4:43 PM, Luciano Coelho wrote:
> > If the requested firmware file size is 0 bytes in the filesytem, we
> > will try to vmalloc(0), which causes a warning:
> >
> > [37834.750274] vmalloc:
On Wed, 2013-01-16 at 11:43 +0800, Ming Lei wrote:
On Tue, Jan 15, 2013 at 4:43 PM, Luciano Coelho coe...@ti.com wrote:
If the requested firmware file size is 0 bytes in the filesytem, we
will try to vmalloc(0), which causes a warning:
[37834.750274] vmalloc: allocation failure: 0 bytes
-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 Kees,
On Wed, 2013-01-16 at 18:53 -0800, Kees Cook wrote:
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any depends on lines in Kconfigs.
Cc: Luciano
: stable [3.7]
Signed-off-by: Luciano Coelho
---
drivers/base/firmware_class.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/base/firmware_class.c b/drivers/base/firmware_class.c
index d814603..b392b35 100644
--- a/drivers/base/firmware_class.c
+++ b/drivers/base
[c007a2d4]
(kthread+0xb4/0xc0)
[37834.893707] [c007a2d4] (kthread+0xb4/0xc0) from [c0015490]
(ret_from_fork+0x14/0x20)
To fix this, check whether the file size is less than or equal to zero
in fw_read_file_contents().
Cc: stable sta...@vger.kernel.org [3.7]
Signed-off-by: Luciano Coelho coe
. Only compile tested.
>
> Signed-off-by: Tejun Heo
> Cc: Luciano Coelho
> Cc: linux-wirel...@vger.kernel.org
> ---
> Please let me know how this patch should be routed. I can take it
> through the workqueue tree if necessary.
>
> Thanks.
It's probably easier if you t
.
Signed-off-by: Tejun Heo t...@kernel.org
Cc: Luciano Coelho coe...@ti.com
Cc: linux-wirel...@vger.kernel.org
---
Please let me know how this patch should be routed. I can take it
through the workqueue tree if necessary.
Thanks.
It's probably easier if you take it via your tree
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:
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
> >> i
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
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.
> &
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
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
On Fri, 2012-11-16 at 12:20 +0530, Tushar Behera wrote:
> No need to check whether unsigned variable is less than 0.
>
> CC: Luciano Coelho
> CC: linux-wirel...@vger.kernel.org
> CC: net...@vger.kernel.org
> Signed-off-by: Tushar Behera
> ---
Applied in the wl12xx.git tr
On Wed, 2012-11-07 at 01:28 +0800, Chuansheng Liu wrote:
> The return value of wait_for_completion_timeout() is always
> >= 0 with unsigned int type.
>
> So the condition "ret < 0" or "ret >= 0" is pointless.
>
> Signed-off-by: liu chuansheng
> ---
Applied and pushed via wl12xx.git.
Thank
On Mon, 2012-11-05 at 15:03 -0800, Kees Cook wrote:
> The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
> while now and is almost always enabled by default. As agreed during the
> Linux kernel summit, remove it from any "depends on" lines in Kconfigs.
>
On Tue, 2012-10-23 at 13:03 -0700, Kees Cook wrote:
> This config item has not carried much meaning for a while now and is
> almost always enabled by default. As agreed during the Linux kernel
> summit, remove it.
>
> CC: Luciano Coelho
> CC: "John W. Linville"
On Sun, 2012-10-21 at 12:52 +0200, Julia Lawall wrote:
> From: Julia Lawall
>
> The function wl12xx_set_power_on is only called twice, once in
> wl12xx_chip_wakeup and once in wl12xx_get_hw_info. On the failure of the
> call in wl12xx_chip_wakeup, the containing function just returns, but on
>
On Sun, 2012-10-21 at 12:52 +0200, Julia Lawall wrote:
From: Julia Lawall julia.law...@lip6.fr
The function wl12xx_set_power_on is only called twice, once in
wl12xx_chip_wakeup and once in wl12xx_get_hw_info. On the failure of the
call in wl12xx_chip_wakeup, the containing function just
On Tue, 2012-10-23 at 13:03 -0700, Kees Cook wrote:
This config item has not carried much meaning for a while now and is
almost always enabled by default. As agreed during the Linux kernel
summit, remove it.
CC: Luciano Coelho coe...@ti.com
CC: John W. Linville linvi...@tuxdriver.com
On Mon, 2012-11-05 at 15:03 -0800, Kees Cook wrote:
The CONFIG_EXPERIMENTAL config item has not carried much meaning for a
while now and is almost always enabled by default. As agreed during the
Linux kernel summit, remove it from any depends on lines in Kconfigs.
CC: Luciano Coelho coe
On Wed, 2012-11-07 at 01:28 +0800, Chuansheng Liu wrote:
The return value of wait_for_completion_timeout() is always
= 0 with unsigned int type.
So the condition ret 0 or ret = 0 is pointless.
Signed-off-by: liu chuansheng chuansheng@intel.com
---
Applied and pushed via wl12xx.git.
On Fri, 2012-11-16 at 12:20 +0530, Tushar Behera wrote:
No need to check whether unsigned variable is less than 0.
CC: Luciano Coelho coe...@ti.com
CC: linux-wirel...@vger.kernel.org
CC: net...@vger.kernel.org
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Applied
Hi,
Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.
Our card simply doesn't get added to the system and we get lots of
Hi,
Since the 32KHz clock was removed from the twl-regulator (0e8e5c34
regulator: twl: Remove references to 32kHz clock from DT bindings),
we've been having problems with our wl12xx chip that is connected
through the omap_hsmmc.
Our card simply doesn't get added to the system and we get lots of
st the files in actual use.
>
> Cc: Luciano Coelho
> Cc: linux-wirel...@vger.kernel.org
> Cc: net...@vger.kernel.org
> Signed-off-by: Tim Gardner
> ---
Applied, thank you!
--
Luca.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel&
in actual use.
Cc: Luciano Coelho coe...@ti.com
Cc: linux-wirel...@vger.kernel.org
Cc: net...@vger.kernel.org
Signed-off-by: Tim Gardner tim.gard...@canonical.com
---
Applied, thank you!
--
Luca.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Wed, 2012-08-29 at 11:13 -0600, Tim Gardner wrote:
> On 08/29/2012 11:01 AM, Luciano Coelho wrote:
> > On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote:
> >> Cc: Luciano Coelho
> >> Cc: "John W. Linville"
> >> Cc: Eliad Peller
> >>
On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote:
> Cc: Luciano Coelho
> Cc: "John W. Linville"
> Cc: Eliad Peller
> Cc: Arik Nemtsov
> Cc: Eyal Shapira
> Cc: linux-wirel...@vger.kernel.org
> Cc: net...@vger.kernel.org
> Signed-off-by: Tim Gardner
On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote:
Cc: Luciano Coelho coe...@ti.com
Cc: John W. Linville linvi...@tuxdriver.com
Cc: Eliad Peller el...@wizery.com
Cc: Arik Nemtsov a...@wizery.com
Cc: Eyal Shapira e...@wizery.com
Cc: linux-wirel...@vger.kernel.org
Cc: net
On Wed, 2012-08-29 at 11:13 -0600, Tim Gardner wrote:
On 08/29/2012 11:01 AM, Luciano Coelho wrote:
On Wed, 2012-08-29 at 08:48 -0600, Tim Gardner wrote:
Cc: Luciano Coelho coe...@ti.com
Cc: John W. Linville linvi...@tuxdriver.com
Cc: Eliad Peller el...@wizery.com
Cc: Arik Nemtsov
201 - 297 of 297 matches
Mail list logo
