linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
Cc: linux-serial@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	magnus.damm@gmail.com, wsa@the-dreams.de, robh@kernel.org,
	peda@axentia.se, geert@linux-m68k.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 6/6] dt-bindings: slave-device: add reg property
Date: Wed, 16 Aug 2017 16:27:31 +0300	[thread overview]
Message-ID: <10586476.xpvXiRN2X6@avalon> (raw)
In-Reply-To: <1502889748-31499-7-git-send-email-ulrich.hecht+renesas@gmail.com>

Hi Ulrich,

Thank you for the patch.

On Wednesday 16 Aug 2017 15:22:28 Ulrich Hecht wrote:
> This adds a new DT property to define the index used by a multiplexer to
> select the device.
> 
> Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> ---
>  Documentation/devicetree/bindings/serial/slave-device.txt | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/serial/slave-device.txt
> b/Documentation/devicetree/bindings/serial/slave-device.txt index
> 40110e0..f9b0783 100644
> --- a/Documentation/devicetree/bindings/serial/slave-device.txt
> +++ b/Documentation/devicetree/bindings/serial/slave-device.txt
> @@ -30,6 +30,8 @@ Optional Properties:
>  		      way to reset the device
>  		    * device baud rate is configured by its firmware but
>  		      there is no way to request the actual settings
> +- reg		: Index used to select the device if it is controlled 
by a
> +		  multiplexer.

The reg property should describe the device address on the bus it is connected 
to. This seems like an abuse of the property to me. The device shouldn't care 
about the multiplexer, I think you should describe the hardware by adding the 
serial device's DT node as a child of the multiplexer's port it is connected 
to.

>  Example:

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2017-08-16 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 13:22 [PATCH 0/6] serdev multiplexing support Ulrich Hecht
2017-08-16 13:22 ` [PATCH 1/6] serdev: add method to set parity Ulrich Hecht
2017-08-16 13:22 ` [PATCH 2/6] serdev: add multiplexer support Ulrich Hecht
2017-08-16 13:22 ` [PATCH 3/6] serial: core: support deferring serdev controller registration Ulrich Hecht
2017-08-16 13:22 ` [PATCH 4/6] max9260: add driver for i2c over GMSL passthrough Ulrich Hecht
2017-08-16 13:22 ` [PATCH 5/6] ARM: dts: blanche: add SCIF1 and MAX9260 deserializer Ulrich Hecht
2017-08-21  8:54   ` Simon Horman
2017-08-16 13:22 ` [PATCH 6/6] dt-bindings: slave-device: add reg property Ulrich Hecht
2017-08-16 13:27   ` Laurent Pinchart [this message]
2017-08-28 12:55 ` [PATCH 0/6] serdev multiplexing support Greg KH

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=10586476.xpvXiRN2X6@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=peda@axentia.se \
    --cc=robh@kernel.org \
    --cc=ulrich.hecht+renesas@gmail.com \
    --cc=wsa@the-dreams.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 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).