On Wed, Dec 18, 2013 at 12:25 AM, Sebastian Reichel s...@ring0.de wrote:
I had a look at both ofono's and freesmartphone.org's implementation
for the GPIO handling and both implementations are very similar. I
think it should be possible to move the state machine described in
[0] into the
[ added agust@ for mpc5xxx, dropped devicetree ]
On Fri, Dec 20, 2013 at 18:34 +0200, Tero Kristo wrote:
Low level register ops are needed for providing SoC or IP block specific
access routines to clock registers. Subsequent patches add support for
the low level ops for the individual clock
[ dropped devicetree, we're clock specific here ]
On Fri, Dec 20, 2013 at 18:34 +0200, Tero Kristo wrote:
Divider clock can now be registered to use low level register access ops.
Preferred initialization method is via clock description.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
From: Mugunthan V N mugunthan...@ti.com
Date: Wed, 18 Dec 2013 21:33:50 +0530
During checking the interrupts with cat /proc/interrupts, it is showing
device name as (null), this change was done with commit id aa1a15e2d where
request_irq is changed to devm_request_irq also changing the irq name
On 2013-12-20 18:04, Tony Lindgren wrote:
This looks odd... Presuming the panel device was probed successfully, it
should always get the gpios or return an error. Only if gpio_is_valid()
returns false for the gpio, it skips it and continues. But in this case,
the gpio number comes from the
On 2013-12-20 18:55, Tony Lindgren wrote:
I bet that's it though. If the display is probed before twl4030 GPIO
is initialized, the GPIO numbers will be 0. I'm using omap2plus_defconfig
which has DSS built as modules.
Yeah this seems to do the trick for me for the built-in DSS on LDP.
