From: Rob Herring <robh@kernel.org>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
nicolas.ferre@atmel.com, boris.brezillon@free-electrons.com,
alexandre.belloni@free-electrons.com, sameo@linux.intel.com,
lee.jones@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH linux-next v9 2/3] mfd: devicetree: add bindings for Atmel Flexcom
Date: Wed, 9 Sep 2015 19:06:19 -0500 [thread overview]
Message-ID: <55F0C97B.80404@kernel.org> (raw)
In-Reply-To: <55F0540F.6000102@atmel.com>
On 09/09/2015 10:45 AM, Cyrille Pitchen wrote:
> Hi Rob,
>
> Le 09/09/2015 01:40, Rob Herring a écrit :
>> On 09/01/2015 09:46 AM, Cyrille Pitchen wrote:
>>> This patch documents the DT bindings for the Atmel Flexcom which will be
>>> introduced by sama5d2x SoCs. These bindings will be used by the actual
>>> Flexcom driver to be sent in another patch.
>>>
>>> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
>>> Acked-by: Boris Brezillon <boris.brezillon@free-electrons.com>
>>> Acked-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
>>
>> A few comments, but in general looks fine.
>>
>>> ---
>>> .../devicetree/bindings/mfd/atmel-flexcom.txt | 67 ++++++++++++++++++++++
>>> 1 file changed, 67 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
>>>
>>> diff --git a/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt b/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
>>> new file mode 100644
>>> index 000000000000..fc3511e41542
>>> --- /dev/null
>>> +++ b/Documentation/devicetree/bindings/mfd/atmel-flexcom.txt
>>> @@ -0,0 +1,67 @@
>>> +* Device tree bindings for Atmel Flexcom (Flexible Serial Communication Unit)
>>> +
>>> +The Atmel Flexcom is just a wrapper which embeds a SPI controller, an I2C
>>> +controller and an USART. Only one function can be used at a time and is chosen
>>> +at boot time according to the device tree.
>>
>> Doesn't the board design choose (unless pins go to a header)?
>>
>
> The function may be chosen once for all by the board design but if we take the
> sama5d2 xplained board as an example, most Flexcoms output their pins to
> headers.
>
>>> +
>>> +Required properties:
>>> +- compatible: Should be "atmel,sama5d2-flexcom"
>>> +- reg: Should be the offset/length value for Flexcom dedicated
>>> + I/O registers (without USART, TWI or SPI registers).
>>> +- clocks: Should be the Flexcom peripheral clock from PMC.
>>> +- #address-cells: Should be <1>
>>> +- #size-cells: Should be <1>
>>> +- ranges: Should be one range for the full I/O register region
>>> + (including USART, TWI and SPI registers).
>>> +- atmel,flexcom-mode: Should be one of the 3 following macros as defined in
>>> + include/dt-bindings/mfd/atmel-flexcom.h:
>>> + - ATMEL_FLEXCOM_MODE_USART for USART
>>> + - ATMEL_FLEXCOM_MODE_SPI for SPI
>>> + - ATMEL_FLEXCOM_MODE_TWI for I2C
>>> +
>>> +Required child:
>>> +a single child device of type matching the "atmel,flexcom-mode" property.
>>
>> Okay, but why not allow all children and use "status"?
>>
>
> That is exactly what was proposed in v6 of this series: allow more than one
> child so possibly all children but only one "available" child (status =
> "okay").
>
> The Flexocm driver still needs to find out the type of device of this
> available child to know which function is to be enabled (USART, I2C or SPI).
> So the "compatible" attribute was parsed using strstr() to search on of the
> patterns "usart", "spi" or "i2c".
>
> However the use of strstr() was discussed to know whether the driver should
> looks for a partial or an exact match of the "compatible" string.
> An exact match would require to keep the Flexcom driver synchonized with the
> 3 other drivers every time one of them introduces a new compatibility string,
> which whould have made every driver more difficult to maintain by creating a
> useless dependency.
> So this implementation relying on the "compatible" attribute was abandoned.
>
> To sum up, no other reliable (and simple) means to guess/extact the device
> type from its DT node was found so we got back to the "atmel,flexcom-mode"
> property.
I wasn't thinking removing this property. If the mode is configured by
the bootloader, then you want to make updates to the configuration as
simple as possible. Updating atmel,flexcom-mode and status for the
children would be much more simple than creating the whole child node.
If that's not a valid usecase, then never mind.
Rob
next prev parent reply other threads:[~2015-09-10 0:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:46 [PATCH linux-next v9 0/3] mfd: flexcom: add a driver for Flexcom Cyrille Pitchen
[not found] ` <cover.1441118159.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-09-01 14:46 ` [PATCH linux-next v9 1/3] mfd: atmel-flexcom: create include file with macros used by DT bindings Cyrille Pitchen
[not found] ` <69844d8092ccbcaef6a3a24d39127ca432462d69.1441118159.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-09-03 15:42 ` Nicolas Ferre
2015-09-08 23:33 ` Rob Herring
2015-09-01 14:46 ` [PATCH linux-next v9 2/3] mfd: devicetree: add bindings for Atmel Flexcom Cyrille Pitchen
[not found] ` <90fa2e0ded92567a29c996658153d833aaa5e411.1441118159.git.cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-09-03 15:56 ` Nicolas Ferre
2015-09-08 23:40 ` Rob Herring
2015-09-09 15:45 ` Cyrille Pitchen
2015-09-10 0:06 ` Rob Herring [this message]
[not found] ` <55F0C97B.80404-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-09-21 12:15 ` Cyrille Pitchen
2015-09-08 16:04 ` [PATCH linux-next v9 0/3] mfd: flexcom: add a driver for Flexcom Cyrille Pitchen
2015-09-08 16:26 ` Lee Jones
2015-09-01 14:46 ` [PATCH linux-next v9 3/3] mfd: atmel-flexcom: add a driver for Atmel Flexible Serial Communication Unit Cyrille Pitchen
2015-09-20 4:19 ` [PATCH linux-next v9 0/3] mfd: flexcom: add a driver for Flexcom Lee Jones
2015-09-23 10:29 ` Nicolas Ferre
[not found] ` <56027F10.1060804-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-09-24 17:37 ` Lee Jones
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=55F0C97B.80404@kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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).