On 11/19/2011 12:37 AM, Tony Lindgren wrote:
* Cousson, Benoit [16 07:27]:
Hi Tony,
That bug is becoming annoying, and a bunch of folks are hitting that issue
during DT dev for 3.3, so it will be cool to fix that ASAP.
OK pulling it in. BTW, next time, please try to base branches on som
Hi Rajendra,
On Mon, Nov 21, 2011 at 11:45 AM, Rajendra Nayak wrote:
> An hwmod with a 'HWMOD_INIT_NO_IDLE' flag set, is left in
> enabled state by the hwmod framework post the initial setup.
> Once a real user of the device (a driver) tries to enable it
> at a later point, the hwmod framework th
On Monday 21 November 2011 03:33 PM, Govindraj wrote:
Hi Rajendra,
On Mon, Nov 21, 2011 at 11:45 AM, Rajendra Nayak wrote:
An hwmod with a 'HWMOD_INIT_NO_IDLE' flag set, is left in
enabled state by the hwmod framework post the initial setup.
Once a real user of the device (a driver) tries to e
An hwmod with a 'HWMOD_INIT_NO_IDLE' flag set, is left in
enabled state by the hwmod framework post the initial setup.
Once a real user of the device (a driver) tries to enable it
at a later point, the hwmod framework throws a WARN() about
the device being already in enabled state.
Fix this by int
Hi Kevin,
On Fri, 2011-11-18 at 11:02 -0800, Kevin Hilman wrote:
> Tero Kristo writes:
>
> > These are needed because runtime PM is disabled during suspend, and
> > it is bad if we get interrupts from the PRCM chain handler during it.
> > Now, PRCM interrupt forwarding is disabled until the susp
On Fri, 2011-11-18 at 21:18 +0200, Felipe Balbi wrote:
> Hi,
>
> On Thu, Nov 17, 2011 at 02:34:46PM -0800, Kevin Hilman wrote:
> > Tero Kristo writes:
> >
> > > Introduce a chained interrupt handler mechanism for the PRCM
> > > interrupt, so that individual PRCM event can cleanly be handled by
>
On Sat, Nov 19, 2011 at 2:54 AM, Kevin Hilman wrote:
> "Govindraj.R" writes:
>
>> Omap-uart can be used as console uart to print early boot
>> messages using earlyprintk so for console uart prevent
>> hwmod reset or idling during bootup.
>>
>> Identify the console_uart set the id and use the cust
On Mon, Nov 21, 2011 at 7:17 PM, Govindraj wrote:
> On Sat, Nov 19, 2011 at 2:54 AM, Kevin Hilman wrote:
>> "Govindraj.R" writes:
>>
>>> Omap-uart can be used as console uart to print early boot
>>> messages using earlyprintk so for console uart prevent
>>> hwmod reset or idling during bootup.
>
On Sun, Nov 20, 2011 at 03:27:19AM +, Paul Walmsley wrote:
> The OMAP-specific parts should be queued up in my/Benoît's/Tony's trees,
> rather than placed directly into -next. Otherwise they are likely to
> generate merge conflicts with other OMAP changes that we may generate.
>
> So I'd su
Hi,
On Mon, Nov 21, 2011 at 9:58 PM, Will Deacon wrote:
> On Sun, Nov 20, 2011 at 03:27:19AM +, Paul Walmsley wrote:
>> The OMAP-specific parts should be queued up in my/Benoît's/Tony's trees,
>> rather than placed directly into -next. Otherwise they are likely to
>> generate merge conflicts
On Mon, Nov 21, 2011 at 02:53:54PM +, Ming Lei wrote:
> On Mon, Nov 21, 2011 at 9:58 PM, Will Deacon wrote:
> > On Sun, Nov 20, 2011 at 03:27:19AM +, Paul Walmsley wrote:
> >> The OMAP-specific parts should be queued up in my/Benoît's/Tony's trees,
> >> rather than placed directly into -ne
On Mon, Nov 21, 2011 at 11:16 PM, Will Deacon wrote:
> On Mon, Nov 21, 2011 at 02:53:54PM +, Ming Lei wrote:
>> On Mon, Nov 21, 2011 at 9:58 PM, Will Deacon wrote:
>> > On Sun, Nov 20, 2011 at 03:27:19AM +, Paul Walmsley wrote:
>> >> The OMAP-specific parts should be queued up in my/Benoî
Hi,
On Tue, Nov 8, 2011 at 12:00 AM, Tarun Kanti DebBarma
wrote:
> Since omap_dm_timer_write_reg/__omap_dm_timer_write is now modified
> to use timer->func_base OCP_CFG should not use this wrapper anymore.
> Instead use __raw_writel() directly and use timer->io_base instead
> to write to OCP_CFG.
Shubhrajyoti D writes:
> For OMAP4 Interrupt enable register is a legacy register.
I don't see anything in the docs mentioning this is legacy. In fact,
that register is used extensivly throughout the driver, even for OMAP4.
I think the CLR/SET registers were added to aid atomically
setting/cle
Rajendra Nayak writes:
> An hwmod with a 'HWMOD_INIT_NO_IDLE' flag set, is left in
> enabled state by the hwmod framework post the initial setup.
> Once a real user of the device (a driver) tries to enable it
> at a later point, the hwmod framework throws a WARN() about
> the device being already
Hi Tony,
On 19.11.2011 04:36, Tony Lindgren wrote:
>> Well, it already boots with DT actually. Did you mean booting with DT
>> and board-generic? I have to admit I don't know how to proceed here:
>
> Good to hear you're already playing with it. Yes, let's work on making
> all the boards work with
Hi all,
A quick refresher: the clock framework APIs in include/linux/clk.h have
allowed platforms to develop their own platform-specific implementations
to manage clocks; this meant that everyone had their own definition of
struct clk, duplicated much code and contributed negatively to the
on-goin
The common clk framework provides clk_prepare and clk_unprepare
implementations. Create an entry for HAVE_CLK_PREPARE so that
GENERIC_CLK can select it.
Signed-off-by: Mike Turquette
---
drivers/clk/Kconfig |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/K
Provide documentation for the common clk structures and APIs. This code
can be found in drivers/clk/ and include/linux/clk.h.
Signed-off-by: Mike Turquette
---
Documentation/clk.txt | 312 +
1 files changed, 312 insertions(+), 0 deletions(-)
cre
The common clk framework is an attempt to define a common struct clk
which can be used by most platforms, and an API that drivers can always
use safely for managing clks.
The net result is consolidation of many different struct clk definitions
and platform-specific clk framework implementations.
Many platforms support simple gateable clks and fixed-rate clks that
should not be re-implemented by every platform.
This patch introduces a gateable clk with a common programming model of
gate control via a write of 1 bit to a register. Both set-to-enable and
clear-to-enable are supported.
Also
Introduces kobject support for the common struct clk, exports per-clk
data via read-only callbacks and models the clk tree topology in sysfs.
Also adds support for generating the clk tree in clk_init and migrating
nodes when input sources are switches in clk_set_parent.
Signed-off-by: Mike Turque
On Tuesday 22 November 2011 12:05 AM, Kevin Hilman wrote:
> Shubhrajyoti D writes:
>
>> For OMAP4 Interrupt enable register is a legacy register.
> I don't see anything in the docs mentioning this is legacy. In fact,
> that register is used extensivly throughout the driver, even for OMAP4.
>
> I
However on OMAP4 we were writing 1 to IRQENABLE_CLR which clears only
the arbitration lost interrupt. The patch intends to fix the same by writing
0 to the IE register.
Signed-off-by: Vikram Pandita
Signed-off-by: Shubhrajyoti D
---
drivers/i2c/busses/i2c-omap.c |6 ++
1 files changed
On Tuesday 22 November 2011 11:31 AM, Shubhrajyoti D wrote:
> However on OMAP4 we were writing 1 to IRQENABLE_CLR which clears only
> the arbitration lost interrupt. The patch intends to fix the same by writing
> 0 to the IE register.
Please ignore this patch I will send another one in a while.
>
25 matches
Mail list logo