Hi,
On Thu, Dec 11, 2014 at 11:13:07PM +0100, Pavel Machek wrote:
> Hi!
>
> > > h4p changes uart speed again after load of the firmware, but I guess
> > > that's ok.
>
> > if you can do it the other way around it would result in a faster
> > init. Depending on how many patches are actually requ
Hi Pavel,
>>> h4p changes uart speed again after load of the firmware, but I guess
>>> that's ok.
>
>> if you can do it the other way around it would result in a faster
>> init. Depending on how many patches are actually required to be
>> loaded.
>
> IIRC driver does two speed changes, so it loo
Hi!
> > h4p changes uart speed again after load of the firmware, but I guess
> > that's ok.
> if you can do it the other way around it would result in a faster
> init. Depending on how many patches are actually required to be
> loaded.
IIRC driver does two speed changes, so it looks to me like
Neil Brown send series which implement what was suggested in previous posts:
https://lkml.org/lkml/2014/12/11/454
On Wed, Dec 10, 2014 at 11:50 PM, s...@debian.org wrote:
> Hi,
>
> On Wed, Dec 10, 2014 at 09:56:22PM +0100, Pavel Machek wrote:
>> On Wed 2014-12-10 18:42:03, Mark Rutland wrote:
>>
The only function of these 'prepare' and 'complete' is to
disable the 'card detect' irq during suspend.
The commit which added this,
commit a48ce884d5819d5df2cf1139ab3c43f8e9e419b3
mmc: omap_hsmmc: Introduce omap_hsmmc_prepare/complete
justified it by the need to avoid the registration of new
Using the common code removes some code duplication, and
makes it easier to switch to using mmc_of_parse() which
will remove more duplication.
As hsmmc has a slightly different interrupt service routine
for card-detect, enhance slot-gpio to allow an alternate
routine to be provided.
Signed-off-by
This ensures that all standard options are available to hsmmc,
In particular, I need cap-power-off-card.
Signed-off-by: NeilBrown
---
drivers/mmc/host/omap_hsmmc.c | 33 -
1 file changed, 8 insertions(+), 25 deletions(-)
diff --git a/drivers/mmc/host/omap_hsmmc
This is resend, rebased on
git://git.linaro.org/people/ulf.hansson/mmc.git next
and so should apply to 3.19-rc1.
omap_hsmmc currently duplicates some work that can be done for
it by common code, and consequently does not benefit from extra
functionality in that common code.
In particular, mmc
On Thu, Dec 11, 2014 at 03:41:16PM -0500, Lennart Sorensen wrote:
> Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
> crystal is not enabled at power up. Instead the CPU falls back to using
> an emulation for the 32KHz clock which is SYSCLK1/610. SYSCLK1 is usually
> 20
Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
crystal is not enabled at power up. Instead the CPU falls back to using
an emulation for the 32KHz clock which is SYSCLK1/610. SYSCLK1 is usually
20MHz on boards so far (which gives an emulated frequency of 32.786KHz),
but
On 12/11/2014 09:34 PM, Nicolae Rosia wrote:
> Hello,
Hi,
> Any updates on this series? I don't see it applied in [1] or [2].
I manage to freeze am335x-evm with those patches and I think Vignesh
is looking into this.
> Regards,
> Nicolae Rosia
Sebastian
--
To unsubscribe from this list: send
Hello,
Any updates on this series? I don't see it applied in [1] or [2].
[1]
https://github.com/RobertCNelson/ti-linux-kernel/commits/ti-linux-3.14.y/drivers/input/touchscreen/ti_am335x_tsc.c
[2]
https://github.com/RobertCNelson/ti-linux-kernel/commits/ti-linux-3.14.y-exp/drivers/input/touchscr
* Sebastian Reichel [141211 09:46]:
> On Thu, Dec 11, 2014 at 08:23:33AM -0600, Felipe Balbi wrote:
> > true, but I'm still a bit iffy wrt that. ABI compatibility breaks and
> > all
>
> Moving the hwmod data to device tree will break the ABI
> compatibility anyways. You wont be able to use an old
On Thu, Dec 11, 2014 at 08:23:33AM -0600, Felipe Balbi wrote:
> Hi,
>
> On Thu, Dec 11, 2014 at 01:52:38AM +0100, Sebastian Reichel wrote:
> > On Wed, Dec 10, 2014 at 08:54:33AM -0600, Felipe Balbi wrote:
> > > Hi,
> > >
> > > (adding linux-omap back to the loop)
> > >
> > > On Wed, Dec 10, 2014
* Sebastian Reichel [141210 16:55]:
> On Wed, Dec 10, 2014 at 08:54:33AM -0600, Felipe Balbi wrote:
> > > @@ -2449,6 +2559,12 @@ static int __init _init(struct omap_hwmod *oh,
> > > void *data)
> > > else if (np && index)
> > > pr_warn("omap_hwmod: %s using broken dt d
Hi,
* Felipe Balbi [141211 06:24]:
> On Thu, Dec 11, 2014 at 01:46:28AM +0100, Sebastian Reichel wrote:
> >
> > Each IP-Core connected to the bus of OMAP processors has
> > three registers, which specify the IP-Core's version, its
> > status and setup of PM features.
> >
> > Required Properties
On 12/11/2014 08:44 AM, Jean-Michel Hautbois wrote:
> Hi !
>
> I have a custom board with a AM3505.
> I am trying to use linux 3.18 and I have difficulties making it work.
> What is needed in order to get it declared in DT ?
usually look at examples of an board file closely resembling the one
that
Hi !
I have a custom board with a AM3505.
I am trying to use linux 3.18 and I have difficulties making it work.
What is needed in order to get it declared in DT ?
Is it still needed to have a board-am3517-myboard.c ?
I have a few drivers like that I need to bring up (a Micrel KSZ8873
for example)
Hi,
On Thu, Dec 11, 2014 at 01:52:38AM +0100, Sebastian Reichel wrote:
> On Wed, Dec 10, 2014 at 08:54:33AM -0600, Felipe Balbi wrote:
> > Hi,
> >
> > (adding linux-omap back to the loop)
> >
> > On Wed, Dec 10, 2014 at 04:20:30PM +0530, Lokesh Vutla wrote:
> > > Hi Felipe,
> > >
> > > On Wedne
Hi,
On Thu, Dec 11, 2014 at 01:46:28AM +0100, Sebastian Reichel wrote:
> On Wed, Dec 10, 2014 at 09:00:49AM -0600, Felipe Balbi wrote:
> > On Wed, Dec 10, 2014 at 04:37:19PM +0530, Lokesh Vutla wrote:
> > > On Wednesday 10 December 2014 03:57 AM, Felipe Balbi wrote:
> > > > In order to get rid of
Hi Pavel,
>>> The TODO file says:
>>>
>>> # > +
>>> # > + skb_queue_tail(&info->txq, fw_skb);
>>> # > + spin_lock_irqsave(&info->lock, flags);
>>> # > + hci_h4p_outb(info, UART_IER, hci_h4p_inb(info, UART_IER) |
>>> # > + UART_IER_THRI);
>>> # > + spin_unlock_i
On 2014-12-11 10:29, Russell King - ARM Linux wrote:
On Wed, Dec 10, 2014 at 10:42:33AM +0100, Marek Szyprowski wrote:
I assume that now it won't be possible to get l2c patches back to -next,
so I will resend them (again...) with the omap related fix.
What, you mean you don't know the fundament
On Wed, Dec 10, 2014 at 10:42:33AM +0100, Marek Szyprowski wrote:
> I assume that now it won't be possible to get l2c patches back to -next,
> so I will resend them (again...) with the omap related fix.
What, you mean you don't know the fundamental rules of kernel development?
No one should ever
23 matches
Mail list logo
