All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney.cavm@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
	Grant Likely <grant.likely@secretlab.ca>,
	Rob Herring <rob.herring@calxeda.com>,
	Ben Dooks <ben-linux@fluff.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree-discuss@lists.ozlabs.org, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH 1/2] i2c: mux: add device tree support
Date: Mon, 23 Apr 2012 10:11:33 -0700	[thread overview]
Message-ID: <4F958D45.1080800@gmail.com> (raw)
In-Reply-To: <4F957F9F.7000309@wwwdotorg.org>

On 04/23/2012 09:13 AM, Stephen Warren wrote:
> On 04/23/2012 05:15 AM, Wolfram Sang wrote:
>> On Tue, Apr 17, 2012 at 12:49:04PM -0600, Stephen Warren wrote:
>>> From: Stephen Warren<swarren@nvidia.com>
>>>
>>> * Define core portions of the DT binding for I2C bus muxes.
>>> * Enhance i2c_add_mux_adapter():
>>> ** Add parameters required for DT support. Update all callers.
>>> ** Set the appropriate adap->dev.of_node for the child bus.
>>> ** Call of_i2c_register_devices() for the child bus.
>>>
>>> Signed-off-by: Stephen Warren<swarren@nvidia.com>
>>
>> David Daney (CCed) posted another variant [1]. Just looking at the
>> patches (and not really using them), I tend to like the approach using
>> <reg>  better. But I am open for discussion, so I'd appreciate your
>> feedback.
>>
>> Regards,
>>
>>     Wolfram
>>
>> [1] http://lkml.org/lkml/2012/4/12/423
>
> Ah, that does look like a reasonable binding.
>

It was arrived at by iterating through several versions with Grant and Rob.

You make at least the third person (after me and Lars-Peter Clausen) 
wanting to use the device tree to configure the I2C muxes.  So at a 
minimum, it shows a need for this.

David Daney.

> I had meant to call out to reviewers the potentially unusual use of
> explicitly named sub-nodes, rather than using the usual reg-based matching.
>
> The main reason I chose named sub-nodes for the busses was so the
> sub-nodes would match the pinctrl named states. However, I think we can
> make the pinctrl numbering match rather than the pinctrl naming instead.
> The only issue is the "idle" state; if we allow it to exist anywhere in
> the pinctrl-names list, it'll make the pinctrl numbering mismatch the
> sub-node numbering. I think we can solve this by forcing the idle state
> to be listed last in pinctrl-names (if it's listed at all). I'll update
> my patches based on that David's patch.


WARNING: multiple messages have this Message-ID (diff)
From: David Daney <ddaney.cavm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	Grant Likely
	<grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>,
	Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
	Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	Linus Walleij
	<linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Lars-Peter Clausen <lars-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
Subject: Re: [PATCH 1/2] i2c: mux: add device tree support
Date: Mon, 23 Apr 2012 10:11:33 -0700	[thread overview]
Message-ID: <4F958D45.1080800@gmail.com> (raw)
In-Reply-To: <4F957F9F.7000309-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 04/23/2012 09:13 AM, Stephen Warren wrote:
> On 04/23/2012 05:15 AM, Wolfram Sang wrote:
>> On Tue, Apr 17, 2012 at 12:49:04PM -0600, Stephen Warren wrote:
>>> From: Stephen Warren<swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>>
>>> * Define core portions of the DT binding for I2C bus muxes.
>>> * Enhance i2c_add_mux_adapter():
>>> ** Add parameters required for DT support. Update all callers.
>>> ** Set the appropriate adap->dev.of_node for the child bus.
>>> ** Call of_i2c_register_devices() for the child bus.
>>>
>>> Signed-off-by: Stephen Warren<swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>>
>> David Daney (CCed) posted another variant [1]. Just looking at the
>> patches (and not really using them), I tend to like the approach using
>> <reg>  better. But I am open for discussion, so I'd appreciate your
>> feedback.
>>
>> Regards,
>>
>>     Wolfram
>>
>> [1] http://lkml.org/lkml/2012/4/12/423
>
> Ah, that does look like a reasonable binding.
>

It was arrived at by iterating through several versions with Grant and Rob.

You make at least the third person (after me and Lars-Peter Clausen) 
wanting to use the device tree to configure the I2C muxes.  So at a 
minimum, it shows a need for this.

David Daney.

> I had meant to call out to reviewers the potentially unusual use of
> explicitly named sub-nodes, rather than using the usual reg-based matching.
>
> The main reason I chose named sub-nodes for the busses was so the
> sub-nodes would match the pinctrl named states. However, I think we can
> make the pinctrl numbering match rather than the pinctrl naming instead.
> The only issue is the "idle" state; if we allow it to exist anywhere in
> the pinctrl-names list, it'll make the pinctrl numbering mismatch the
> sub-node numbering. I think we can solve this by forcing the idle state
> to be listed last in pinctrl-names (if it's listed at all). I'll update
> my patches based on that David's patch.

  parent reply	other threads:[~2012-04-23 17:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 18:49 [PATCH 1/2] i2c: mux: add device tree support Stephen Warren
2012-04-17 18:49 ` Stephen Warren
2012-04-17 18:49 ` [PATCH 2/2] i2c: Add generic I2C multiplexer using pinctrl API Stephen Warren
2012-04-17 18:49   ` Stephen Warren
2012-04-17 19:50   ` Linus Walleij
2012-04-17 19:50     ` Linus Walleij
2012-04-23 11:15 ` [PATCH 1/2] i2c: mux: add device tree support Wolfram Sang
2012-04-23 11:15   ` Wolfram Sang
2012-04-23 16:13   ` Stephen Warren
2012-04-23 16:13     ` Stephen Warren
2012-04-23 17:00     ` Wolfram Sang
2012-04-23 17:00       ` Wolfram Sang
2012-04-23 17:11     ` David Daney [this message]
2012-04-23 17:11       ` David Daney

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=4F958D45.1080800@gmail.com \
    --to=ddaney.cavm@gmail.com \
    --cc=ben-linux@fluff.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@nvidia.com \
    --cc=swarren@wwwdotorg.org \
    --cc=w.sang@pengutronix.de \
    /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.