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 depend on SDIO to function.
Too bad things break and even when
On 12/19/2012 10:45 AM, 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 depend on SDIO to
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 and report things when I see them.
Well, it's a recursive
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 and
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 that coincidentally made a difference,
but we don't know what they
On 12/19/2012 11:56 AM, 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 configure non essential pads, clocks, dplls.
Which means that _essential_ clocks and pads are no longer configured.
Meanwhile
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 that
Hi,
+Sricharan who commited that
On Wed, Dec 19, 2012 at 11:56:20AM +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
On 12/19/2012 02:01 PM, Felipe Balbi wrote:
Hi,
+Sricharan who commited that
On Wed, Dec 19, 2012 at 11:56:20AM +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
Hi,
On Wed, Dec 19, 2012 at 02:51:14PM +0100, Benoit Cousson wrote:
On 12/19/2012 02:01 PM, Felipe Balbi wrote:
Hi,
+Sricharan who commited that
On Wed, Dec 19, 2012 at 11:56:20AM +0100, Peter Ujfalusi wrote:
On 12/19/2012 11:45 AM, Luciano Coelho wrote:
Well, we still haven't
On Wed, Dec 19, 2012 at 02:51:14PM +0100, Benoit Cousson wrote:
Regarding the 32k clock, I noticed as well that the OMAP4460 panda
u-boot is the only one to enable it at boot time, and thus this is the
only board that can probe the wilink chip properly as of today.
Well, there was nothing in
On 12/19/2012 02:58 PM, Luciano Coelho wrote:
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
* Peter Ujfalusi peter.ujfal...@ti.com [121219 02:20]:
On 12/19/2012 11:09 AM, Mark Brown wrote:
On Wed, Dec 19, 2012 at 11:00:32AM +0100, Peter Ujfalusi wrote:
I don't know the state of the common clock framework for OMAPs. Is it
already
up in 3.7? Or going for 3.8? 3.9? 3.10?...
Hi,
On Thu, Nov 15, 2012 at 10:31:33AM +0200, Luciano Coelho wrote:
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.
14 matches
Mail list logo
