From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
AnilKumar Ch <anilkumar@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/4] arm/dts: regulator: Add tps65910 device tree data
Date: Mon, 27 Aug 2012 09:51:38 -0700 [thread overview]
Message-ID: <20120827165137.GL4339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120824201634.GZ11011@atomide.com>
On Fri, Aug 24, 2012 at 01:16:34PM -0700, Tony Lindgren wrote:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [120821 11:09]:
> > The board shouldn't have to define the regulators, the regulator driver
> > really ought to be able to figure out that they're there by itself if
> > there's no configuration based purely on knowing which chip is there.
> > From that point of view it's OK for the chip .dtsi to have them (though
> > ideally the driver wouldn't *need* that either) which was what was
> > happening here.
> So I assume no changes needed here then?
Seems that way.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/4] arm/dts: regulator: Add tps65910 device tree data
Date: Mon, 27 Aug 2012 09:51:38 -0700 [thread overview]
Message-ID: <20120827165137.GL4339@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120824201634.GZ11011@atomide.com>
On Fri, Aug 24, 2012 at 01:16:34PM -0700, Tony Lindgren wrote:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [120821 11:09]:
> > The board shouldn't have to define the regulators, the regulator driver
> > really ought to be able to figure out that they're there by itself if
> > there's no configuration based purely on knowing which chip is there.
> > From that point of view it's OK for the chip .dtsi to have them (though
> > ideally the driver wouldn't *need* that either) which was what was
> > happening here.
> So I assume no changes needed here then?
Seems that way.
next prev parent reply other threads:[~2012-08-27 16:51 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 11:17 [PATCH v3 0/4] Add AM33XX regulators device tree data AnilKumar Ch
2012-08-21 11:17 ` AnilKumar Ch
2012-08-21 11:17 ` [PATCH v3 1/4] arm/dts: regulator: Add tps65910 " AnilKumar Ch
2012-08-21 11:17 ` AnilKumar Ch
2012-08-21 15:48 ` Stephen Warren
2012-08-21 15:48 ` Stephen Warren
2012-08-21 16:38 ` Mark Brown
2012-08-21 16:38 ` Mark Brown
2012-08-21 18:05 ` Stephen Warren
2012-08-21 18:05 ` Stephen Warren
2012-08-21 18:08 ` Mark Brown
2012-08-21 18:08 ` Mark Brown
2012-08-24 20:16 ` Tony Lindgren
2012-08-24 20:16 ` Tony Lindgren
2012-08-27 16:51 ` Mark Brown [this message]
2012-08-27 16:51 ` Mark Brown
2012-08-21 11:17 ` [PATCH v3 2/4] arm/dts: regulator: Add tps65217 " AnilKumar Ch
2012-08-21 11:17 ` AnilKumar Ch
2012-08-21 11:17 ` [PATCH v3 3/4] arm/dts: Add tps65910 regulator DT data to am335x-evm.dts AnilKumar Ch
2012-08-21 11:17 ` AnilKumar Ch
2012-08-21 11:17 ` [PATCH v3 4/4] arm/dts: Add tps65217 regulator DT data to am335x-bone.dts AnilKumar Ch
2012-08-21 11:17 ` AnilKumar Ch
2012-08-23 14:13 ` Koen Kooi
2012-08-23 14:13 ` Koen Kooi
2012-08-24 5:50 ` AnilKumar, Chimata
2012-08-24 5:50 ` AnilKumar, Chimata
2012-08-24 6:28 ` Koen Kooi
2012-08-24 6:28 ` Koen Kooi
2012-08-24 7:26 ` AnilKumar, Chimata
2012-08-24 7:26 ` AnilKumar, Chimata
2012-08-24 7:56 ` Koen Kooi
2012-08-24 7:56 ` Koen Kooi
2012-08-24 8:02 ` Koen Kooi
2012-08-24 8:02 ` Koen Kooi
2012-08-28 5:34 ` AnilKumar, Chimata
2012-08-28 5:34 ` AnilKumar, Chimata
2012-09-05 13:29 ` Koen Kooi
2012-09-05 13:29 ` Koen Kooi
2012-09-05 14:24 ` Matt Porter
2012-09-05 14:24 ` Matt Porter
2012-09-05 14:29 ` Koen Kooi
2012-09-05 14:29 ` Koen Kooi
2012-09-08 6:38 ` AnilKumar, Chimata
2012-09-08 6:38 ` AnilKumar, Chimata
2012-09-10 16:26 ` Matt Porter
2012-09-10 16:26 ` Matt Porter
2012-08-21 13:57 ` [PATCH v3 0/4] Add AM33XX regulators device tree data Mark Brown
2012-08-21 13:57 ` Mark Brown
2012-08-30 21:01 ` Tony Lindgren
2012-08-30 21:01 ` Tony Lindgren
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=20120827165137.GL4339@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=swarren@wwwdotorg.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.