From: Philipp Zabel <p.zabel@pengutronix.de>
To: Steve Longerbeam <slongerbeam@gmail.com>
Cc: Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: [RFC 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings
Date: Wed, 19 Apr 2017 13:47:31 +0200 [thread overview]
Message-ID: <1492602451.2970.90.camel@pengutronix.de> (raw)
In-Reply-To: <d6d32063-5df3-3848-32f5-824c500a8927@gmail.com>
On Thu, 2017-04-13 at 18:03 -0700, Steve Longerbeam wrote:
>
> On 04/13/2017 08:48 AM, Philipp Zabel wrote:
> > This adds device tree binding documentation for mmio-based syscon
> > multiplexers controlled by a single bitfield in a syscon register
> > range.
>
> Nice! (you beat me to it, I was about to embark on this myself :)
>
> Looks good to me, just some minor comments below.
>
[...]
> > +Define a syscon bitfield to be used to control a multiplexer. The parent
> I think "Define a register bitfield to be used ..." is more clear.
[...]
> > +- compatible : "gpio-mux"
> Er, "mmio-mux"
I'll change those, thanks.
[...]
> > +Example:
> > +
> > + syscon {
> > + compatible = "syscon";
> > +
> > + mux: mux-controller@3 {
> > + compatible = "mmio-mux";
> > + reg = <0x3>;
> > + bit-mask = <0x1>;
> > + bit-shift = <5>;
> > + #mux-control-cells = <0>;
> > + };
> > + };
> > +
> > + video-mux {
>
> I like this as an example consumer of a mmio-mux, but just
> the same some might argue this doesn't really fit here.
I don't think this is a problem, of course assuming that this video-mux
binding will actually come into existence.
regards
Philipp
next prev parent reply other threads:[~2017-04-19 11:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 15:48 [RFC 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings Philipp Zabel
2017-04-13 15:48 ` [RFC 2/2] mux: mmio-based syscon mux controller Philipp Zabel
2017-04-14 1:09 ` Steve Longerbeam
2017-04-19 11:50 ` Philipp Zabel
2017-04-19 11:58 ` Peter Rosin
2017-04-19 15:27 ` Philipp Zabel
2017-04-19 16:23 ` Steve Longerbeam
2017-04-19 16:32 ` Philipp Zabel
2017-04-19 16:42 ` Peter Rosin
2017-04-14 1:03 ` [RFC 1/2] dt-bindings: add mmio-based syscon mux controller DT bindings Steve Longerbeam
2017-04-19 11:47 ` Philipp Zabel [this message]
2017-04-18 8:19 ` Philipp Zabel
2017-04-18 10:08 ` Sakari Ailus
2017-04-18 10:34 ` Pavel Machek
2017-04-18 10:55 ` Sakari Ailus
2017-04-18 11:51 ` Pavel Machek
2017-04-18 10:51 ` Philipp Zabel
2017-04-19 22:09 ` Rob Herring
2017-04-20 8:14 ` Philipp Zabel
2017-04-20 11:57 ` Peter Rosin
2017-04-20 13:03 ` Philipp Zabel
2017-04-20 13:39 ` Rob Herring
2017-04-20 13:32 ` Peter Rosin
2017-04-20 14:13 ` Peter Rosin
2017-04-20 14:50 ` Philipp Zabel
2017-04-20 15:01 ` Peter Rosin
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=1492602451.2970.90.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=slongerbeam@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).