On Mon, Apr 15, 2013 at 6:58 PM, Stephen Warren wrote:
> On 04/14/2013 02:53 PM, Linus Walleij wrote:
>> This is a pretty hard design pattern to properly replicate in every such
>> driver is it not?
>
> Well, instead of adding .request_irq() to the irqchip, and then making
> each driver call gpio
On Thu, 2013-04-25 at 20:38 -0700, Tony Lindgren wrote:
> Otherwise SDIO cards won't necessarily work when booted with
> device tree as we will never power down the SDIO cards. This
> means the SDIO card reset does not happen which at least some
> WLAN controllers expect to happen with ifconfig wla
On Thu, 2013-04-25 at 20:52 -0700, Tony Lindgren wrote:
> This should work assuming the board-4430sdp.c works, but it seems
> that I don't have the "1283 PG 2.21 connectivity device" on
> my blaze. Anybody got a spare connectivity device for blaze?
>
> Also, if somebody has the schematics, please
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
> Cc: Benoit Cousson
> Cc: Rajendra Nayak
> Cc: devicetree-disc...@lists.ozl
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 doin
From: Wei Yongjun
Add the missing platform_device_put() before return from
omap2430_probe() in the error handling case.
Introduced by commit ca784be36cc725bca9b526eba342de7550329731
(usb: start using the control module driver)
Signed-off-by: Wei Yongjun
---
drivers/usb/musb/omap2430.c | 3 ++-
This should work assuming the board-4430sdp.c works, but it seems
that I don't have the "1283 PG 2.21 connectivity device" on
my blaze. Anybody got a spare connectivity device for blaze?
Also, if somebody has the schematics, please provide a patch
for the missing GPIO muxes for blaze, see the the
This is needed to get wl12xx working with device tree based
booting.
Note that we claim the various GPIO inputs in the regulator
as the proper muxing is needed to enable and disable the
regulator.
Also, we want to use non-removable instead of ti,non-removable
as the ti,non-removable also sets no_
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
Cc: Benoit Cousson
Cc: Rajendra Nayak
Cc: devicetree-disc...@lists.ozlabs.org
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/devices.c
Hi all,
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.
There are various fixes pending posted recently, but at least the
fix "[PATCH] mmc: omap_h
Otherwise SDIO cards won't necessarily work when booted with
device tree as we will never power down the SDIO cards. This
means the SDIO card reset does not happen which at least some
WLAN controllers expect to happen with ifconfig wlan0 down.
The PBIAS voltage is only available for the first cont
On 04/22/2013 03:54 AM, Andreas Fenkart wrote:
> When a gpio interrupt is masked, the gpio event will still be latched in
> the interrupt status register so when you unmask it later you may get an
> interrupt straight away. However, if the interrupt is disabled then gpio
> events occurring will no
On 04/22/2013 03:54 AM, Andreas Fenkart wrote:
> When a gpio interrupt is masked, the gpio event will still be latched in
> the interrupt status register so when you unmask it later you may get an
> interrupt straight away. However, if the interrupt is disabled then gpio
> events occurring will no
Hi Sourav,
Sourav Poddar writes:
> Hi Kevin,
> On Thursday 25 April 2013 03:45 AM, Kevin Hilman wrote:
>> Sourav Poddar writes:
>>
>>> Remove "no_idle_on_suspend" check, since respective
>>> driver should be able to prevent idling of a
>>> device whenever required.
>>>
>>> Driver's can get same
On Thu, 2013-04-25 at 03:56 -0400, David Miller wrote:
> From: Mugunthan V N
> Date: Mon, 22 Apr 2013 23:50:36 +0530
>
> > In earlier case phy fixup are added in board file as this is no more the
> > case
> > so adding support for phy register fixup in Device Tree
> >
> > Signed-off-by: Mugunth
* Roger Quadros [130422 00:15]:
> On 04/19/2013 06:43 PM, Tony Lindgren wrote:
> > * Roger Quadros [130419 03:02]:
> >> Hi Benoit/Tony
> >>
> >> I've consolidated all the USB host device tree patches for Panda and
> >> Beagles
> >> to one place and addressed Tony's comments.
> >>
> >> NOTE: patc
HI,
On Thu, Apr 25, 2013 at 08:01:20AM -0700, Tony Lindgren wrote:
> > > > > >>>2. MUSB fails with legacy booting and DT on panda es
> > > > > >>>
> > > > > >>>With both legacy and DT booting I get something like:
> > > > > >>>
> > > > > >>>HS USB OTG: no transceiver configured
* Felipe Balbi [130425 02:10]:
> On Wed, Apr 24, 2013 at 12:23:30PM -0700, Tony Lindgren wrote:
> > * Tony Lindgren [130424 12:13]:
> > > * Kishon Vijay Abraham I [130423 22:46]:
> > > > Hi Tony,
> > > >
> > > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote:
> > > > >* Tony Lindgren
Tony Lindgren writes:
> * Santosh Shilimkar [130419 10:56]:
>> On Friday 19 April 2013 11:14 PM, Tony Lindgren wrote:
>> > * Santosh Shilimkar [130419 10:43]:
>> >> On Friday 19 April 2013 10:43 PM, Tony Lindgren wrote:
>> >>> Hi all,
>> >>>
>> >>> Here's a list of breakage I've noticed so far
On 4/25/2013 1:26 PM, David Miller wrote:
From: Mugunthan V N
Date: Mon, 22 Apr 2013 23:50:36 +0530
In earlier case phy fixup are added in board file as this is no more the case
so adding support for phy register fixup in Device Tree
Signed-off-by: Mugunthan V N
When people put a series of
Hi,
On Wed, Apr 24, 2013 at 12:23:30PM -0700, Tony Lindgren wrote:
> * Tony Lindgren [130424 12:13]:
> > * Kishon Vijay Abraham I [130423 22:46]:
> > > Hi Tony,
> > >
> > > On Wednesday 24 April 2013 04:46 AM, Tony Lindgren wrote:
> > > >* Tony Lindgren [130423 14:37]:
> > > >>* Tony Lindgren
Disable overlay via ovl->disable() interface, which will
properly set flags in cache and GO bits for managers.
This allows overlay user to re-enable it on next frame,
thus recovering from FIFO underflows.
Signed-off-by: Sergey Kibrik
---
drivers/video/omap2/dss/dispc-compat.c |3 +--
1 file
From: Mugunthan V N
Date: Mon, 22 Apr 2013 23:50:36 +0530
> In earlier case phy fixup are added in board file as this is no more the case
> so adding support for phy register fixup in Device Tree
>
> Signed-off-by: Mugunthan V N
When people put a series of undocumented PHY register writes usin
On Wednesday 24 April 2013 09:58 PM, Mike Turquette wrote:
> Quoting Nishanth Menon (2013-04-14 14:19:17)
>> Overall strategy introduced here is simple: a clock node described in
>> device tree blob is used to identify the exact clock provided in the
>> SoC specific data. This is then linked back u
24 matches
Mail list logo
