All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"AnilKumar, Chimata" <anilkumar@ti.com>
Subject: Re: [PATCH RESEND 1/4] ARM: OMAP2+: AM33XX: Add tps65910 device tree data
Date: Mon, 23 Jul 2012 14:48:20 +0100	[thread overview]
Message-ID: <500D5624.4010505@linaro.org> (raw)
In-Reply-To: <20120723133400.GU4435@opensource.wolfsonmicro.com>

On 23/07/12 14:34, Mark Brown wrote:
> On Mon, Jul 23, 2012 at 01:23:50PM +0000, AnilKumar, Chimata wrote:
>
>> By the way, if we look at all the regulator added (DT supported) till now have
>> the similar problem.
>
>> arch/arm/boot/dts/imx6q.dtsi
>
> This is fine - the SoC contains integrated regulators which supply other
> bits of the Soc so we can be confident that the hookup is good just
> based on the silicon.
>
>> arch/arm/boot/dts/twl4030.dtsi
>> arch/arm/boot/dts/twl6030.dtsi
>
> These appear to have similar issues and should be fixed, at least as far
> as the voltage ranges go.
>
>> arch/arm/boot/dts/db8500.dtsi
>
> I'm not actually seeing anything terribly problematic here, though the
> regulator-name properties should really be removed as they're fairly
> useless and seem to be missing the point of having the property.

I've missed the context of the thread, so can't comment, but I'm happy 
to remove the regulator-name properties from db8500.dts. Adding to my TODO.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 1/4] ARM: OMAP2+: AM33XX: Add tps65910 device tree data
Date: Mon, 23 Jul 2012 14:48:20 +0100	[thread overview]
Message-ID: <500D5624.4010505@linaro.org> (raw)
In-Reply-To: <20120723133400.GU4435@opensource.wolfsonmicro.com>

On 23/07/12 14:34, Mark Brown wrote:
> On Mon, Jul 23, 2012 at 01:23:50PM +0000, AnilKumar, Chimata wrote:
>
>> By the way, if we look at all the regulator added (DT supported) till now have
>> the similar problem.
>
>> arch/arm/boot/dts/imx6q.dtsi
>
> This is fine - the SoC contains integrated regulators which supply other
> bits of the Soc so we can be confident that the hookup is good just
> based on the silicon.
>
>> arch/arm/boot/dts/twl4030.dtsi
>> arch/arm/boot/dts/twl6030.dtsi
>
> These appear to have similar issues and should be fixed, at least as far
> as the voltage ranges go.
>
>> arch/arm/boot/dts/db8500.dtsi
>
> I'm not actually seeing anything terribly problematic here, though the
> regulator-name properties should really be removed as they're fairly
> useless and seem to be missing the point of having the property.

I've missed the context of the thread, so can't comment, but I'm happy 
to remove the regulator-name properties from db8500.dts. Adding to my TODO.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-07-23 13:48 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  6:46 [PATCH 0/4] Add AM33XX regulators device tree data AnilKumar Ch
2012-07-20  6:46 ` AnilKumar Ch
2012-07-20  6:46 ` [PATCH RESEND 1/4] ARM: OMAP2+: AM33XX: Add tps65910 " AnilKumar Ch
2012-07-20  6:46   ` AnilKumar Ch
2012-07-20  9:59   ` Mark Brown
2012-07-20  9:59     ` Mark Brown
2012-07-20 11:27     ` AnilKumar, Chimata
2012-07-20 11:27       ` AnilKumar, Chimata
2012-07-20 11:38       ` Mark Brown
2012-07-20 11:38         ` Mark Brown
2012-07-23  7:06         ` AnilKumar, Chimata
2012-07-23  7:06           ` AnilKumar, Chimata
2012-07-23 13:23         ` AnilKumar, Chimata
2012-07-23 13:23           ` AnilKumar, Chimata
2012-07-23 13:34           ` Mark Brown
2012-07-23 13:34             ` Mark Brown
2012-07-23 13:48             ` Lee Jones [this message]
2012-07-23 13:48               ` Lee Jones
2012-08-28 11:26             ` Lee Jones
2012-08-28 11:26               ` Lee Jones
2012-08-28 17:21               ` Mark Brown
2012-08-28 17:21                 ` Mark Brown
2012-08-29  8:31                 ` Lee Jones
2012-08-29  8:31                   ` Lee Jones
2012-08-30 16:59                   ` Mark Brown
2012-08-30 16:59                     ` Mark Brown
2012-07-20  6:46 ` [PATCH RESEND 2/4] ARM: OMAP2+: AM33XX: Add tps65217 " AnilKumar Ch
2012-07-20  6:46   ` AnilKumar Ch
2012-07-20 10:01   ` Mark Brown
2012-07-20 10:01     ` Mark Brown
2012-07-20  6:46 ` [PATCH 3/4] arm/dts: Add tps65910 regulator DT data to am335x-evm.dts AnilKumar Ch
2012-07-20  6:46   ` AnilKumar Ch
2012-07-20  6:46 ` [PATCH 4/4] arm/dts: Add tps65217 regulator DT data to am335x-bone.dts AnilKumar Ch
2012-07-20  6:46   ` AnilKumar Ch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=500D5624.4010505@linaro.org \
    --to=lee.jones@linaro.org \
    --cc=anilkumar@ti.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.