* Kevin Hilman [120515 13:17]:
> Tony Lindgren writes:
>
> [...]
>
> > That's already merged as 8259573b (ARM: OMAP2+: nand: Make
> > board_onenand_init()
> > visible to board code) so we need to apply it as a fix.
> >
> > Can you do a fix with
* Kevin Hilman [120515 11:17]:
> Tony Lindgren writes:
>
> > * Javier Martinez Canillas [120427 02:33]:
> >> On Wed, Apr 25, 2012 at 9:59 AM, Enric Balletbò i Serra
> >> wrote:
> >> >
> >> > Tony, as this is a fix ,may be inc
* Javier Martinez Canillas [120427 02:33]:
> On Wed, Apr 25, 2012 at 9:59 AM, Enric Balletbò i Serra
> wrote:
> >
> > Tony, as this is a fix ,may be included ?
> >
> > Acked-by: Enric Balletbo i Serra
> > Tested-by: Enric Balletbo i Serra
> >
> > Cheers,
> > Enric
>
> Hi Tony, Russel:
>
>
* Mark Brown [120321 12:11]:
> On Wed, Mar 21, 2012 at 11:38:58AM -0700, Saravana Kannan wrote:
>
> > >So it would be interesting to know more about why you (or anyone else)
> > >perceive that the Kconfig changes would be harmful.
>
> > But the enthusiasm of the clock driver developers doesn't
>
* Rajendra Nayak [120223 19:29]:
> On Friday 24 February 2012 12:27 AM, Tony Lindgren wrote:
> >>--- a/arch/arm/boot/dts/omap3.dtsi
> >>+++ b/arch/arm/boot/dts/omap3.dtsi
> >>@@ -113,5 +113,31 @@
> >>#size-cells =<0&g
> --- a/arch/arm/boot/dts/omap3.dtsi
> +++ b/arch/arm/boot/dts/omap3.dtsi
> @@ -113,5 +113,31 @@
> #size-cells = <0>;
> ti,hwmods = "i2c3";
> };
> +
> + mmc1: mmc@1 {
> + compatible = "ti,omap2-hsmmc";
> +
* Greg KH [111214 10:27]:
> On Wed, Dec 14, 2011 at 05:18:43PM +, Alan Cox wrote:
> > On Wed, 14 Dec 2011 07:20:13 -0800
> > Kevin Hilman wrote:
> >
> > > Greg, Alan,
> > >
> > > Rajendra Nayak writes:
> > >
> > > > v3 is rebased on top of the latest serial runtime
> > > > patches[1] and
* Rob Herring [111216 13:30]:
> Tony,
>
> On 12/16/2011 03:57 PM, Tony Lindgren wrote:
> > Rob,
> >
> > * Rob Herring [111214 05:16]:
> >> On 12/14/2011 05:55 AM, Rajendra Nayak wrote:
> >>> v3 is rebased on top of the latest serial runtime
>
Rob,
* Rob Herring [111214 05:16]:
> On 12/14/2011 05:55 AM, Rajendra Nayak wrote:
> > v3 is rebased on top of the latest serial runtime
> > patches[1] and boot tested with/without DT on OMAP4
> > SDP and OMAP4 Panda boards.
> >
> > Patches can be found here..
> > git://gitorious.org/omap-pm/lin
* Paul Walmsley [111216 04:18]:
>
> From: Rajendra Nayak
>
> 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 W
Add minimal device tree support for omap2420 and omap2430
Signed-off-by: Tony Lindgren
--- /dev/null
+++ b/arch/arm/boot/dts/omap2.dtsi
@@ -0,0 +1,67 @@
+/*
+ * Device Tree Source for OMAP2 SoC
+ *
+ * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
+ *
+ * This file is
f course won't mount and the file should be separate
for n800 and and n810.. So this patch is not yet quite
ready to go.
Regards,
Tony
From: Tony Lindgren
Date: Thu, 15 Dec 2011 13:04:31 -0800
Subject: [PATCH] arm/dts: Add minimal n8x0 device tree support
Add minimal n8x0 device tree supp
* Cousson, Benoit [111215 01:34]:
> Hi Tony,
>
> On 12/15/2011 7:52 AM, Rajendra Nayak wrote:
> >On Thursday 15 December 2011 12:55 AM, Tony Lindgren wrote:
> >>* Rajendra Nayak [111214 03:24]:
> >>>Pass minimal data needed for console boot, from dt, for
&
* Rajendra Nayak [111214 03:24]:
> Pass minimal data needed for console boot, from dt, for
> OMAP4 panda/sdp and OMAP3 beagle boards, and get rid of the
> static initialization from generic board file.
>
> Acked-by: Rob Herring
> Signed-off-by: Rajendra Nayak
This we can't merge because this b
Hi,
* Linus Walleij [24 01:29]:
> On Tue, Nov 22, 2011 at 6:54 PM, Tony Lindgren wrote:
>
> > Note that with device tree things get simpler for muxing as we can
> > get rid of the hardcoded grouping of pins in mux drivers. Instead of
> > hardcoded pingroups, t
* Russell King - ARM Linux [23 14:07]:
> On Wed, Nov 23, 2011 at 10:55:19AM -0800, Tony Lindgren wrote:
> > What else are you aware of that is really needed early for clocks other
> > than clockevent?
>
> TWD will lose its auto-calibration. Then there's variou
* Mark Brown [23 10:34]:
> On Wed, Nov 23, 2011 at 10:55:19AM -0800, Tony Lindgren wrote:
> > * Russell King - ARM Linux [23 09:31]:
>
> > > Keep the clk API as a fundamental thing which should be initialized early
> > > so we don't have to in
* Russell King - ARM Linux [23 09:31]:
> On Wed, Nov 23, 2011 at 08:59:04AM -0800, Tony Lindgren wrote:
> > ..let's plan on getting rid of the early usage of clocks instead so
> > you don't have the issue of deferring stuff.
>
> No - we have too many platforms
Hi Mike,
* Greg KH [22 10:51]:
> On Tue, Nov 22, 2011 at 09:57:41AM -0800, Mike Turquette wrote:
> > > Ah, comments like this warm my heart.
> > >
> > > Come on, no abusing the kobject code please, if have problems with how
> > > the kernel core works, and it doesn't do things you want it to,
* Linus Walleij [22 03:30]:
> On Tue, Nov 22, 2011 at 12:09 PM, Thomas Abraham
> wrote:
> > On 17 November 2011 19:27, Linus Walleij wrote:
> >>
> >> Maybe I'm mistaken about the device tree ambitions, but
> >> I was sort of hoping that it would not contain too much
> >> custom magic numbers
* Rajendra Nayak [14 04:05]:
> --- /dev/null
> +++ b/drivers/pinctrl/pinmux-omap.c
> @@ -0,0 +1,735 @@
> +
> +/* omap4 core pads */
> +static const struct pinctrl_pin_desc omap4_core_pads[] = {
> + PINCTRL_PIN(0, "c12"),
> + PINCTRL_PIN(1, "d12"),
> + PINCTRL_PIN(2, "c13"),
...
Le
* Grant Likely [111024 12:31]:
> On Mon, Oct 24, 2011 at 09:48:19AM +0200, Linus Walleij wrote:
> > On Mon, Oct 24, 2011 at 9:36 AM, Grant Likely
> > wrote:
> > > On Mon, Oct 24, 2011 at 09:26:38AM +0200, Linus Walleij wrote:
> > (...)
> > >> I was more thinking along the lines of one device per
ches the PM code.
Or if Kevin wants to take the series, here's my ack for the series:
Acked-by: Tony Lindgren
Regards,
Tony
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
* Vishwanath BS [100924 03:50]:
> There is no need to keep omap3 sleep code in SRAM. This code can be run very
> well on DDR. This would help us to instrument CPUIdle latencies.
Uhh, are you sure about this? To me it sounds like you're then
relying on the code running from the cache for off-idle?
* Tony Lindgren [100924 11:53]:
> * Vishwanath BS [100924 03:50]:
> > There is no need to keep omap3 sleep code in SRAM. This code can be run very
> > well on DDR. This would help us to instrument CPUIdle latencies.
>
> Uhh, are you sure about this? To me it sounds like you
25 matches
Mail list logo
