devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Mark Brown <broonie@kernel.org>
Cc: linux-pwm@vger.kernel.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	"arm@kernel.org" <arm@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Olof Johansson <olof@lixom.net>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: PWM...
Date: Tue, 21 Jan 2014 09:39:22 +0900	[thread overview]
Message-ID: <20140121003922.GA31997@verge.net.au> (raw)
In-Reply-To: <20140120161147.GS17314@sirena.org.uk>

On Mon, Jan 20, 2014 at 04:11:47PM +0000, Mark Brown wrote:
> On Mon, Jan 20, 2014 at 09:14:46AM +0900, Simon Horman wrote:
> > On Sun, Jan 19, 2014 at 09:26:40PM +0100, Arnd Bergmann wrote:
> 
> > > Right: if you change an existing dts file from #pwm-cells=<2> to
> > > #pwm-cells=<3>, that requires changing all references to the pwm
> 
> > Would this change imply that old dtbs would no longer work with new kernels?
> 
> So long as the code can still handle both values for #pwm-cells existing
> DTBs should work fine.

Thanks, as long as that is the case I have no objections at this time.

  reply	other threads:[~2014-01-21  0:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140119164956.GR15937@n2100.arm.linux.org.uk>
2014-01-19 19:03 ` PWM Olof Johansson
2014-01-19 19:08   ` PWM Arnd Bergmann
2014-01-19 19:11     ` PWM Olof Johansson
2014-01-19 19:30       ` PWM Russell King - ARM Linux
2014-01-19 20:26         ` PWM Arnd Bergmann
2014-01-19 23:33           ` PWM Olof Johansson
2014-01-20  0:14           ` PWM Simon Horman
2014-01-20  7:24             ` PWM Sascha Hauer
2014-01-20 16:11             ` PWM Mark Brown
2014-01-21  0:39               ` Simon Horman [this message]
2014-01-20  7:21   ` PWM Sascha Hauer

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=20140121003922.GA31997@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=olof@lixom.net \
    --cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).