From: Jonathan Cameron <jic23@kernel.org>
To: Fabrice Gasnier <fabrice.gasnier@st.com>,
linux@armlinux.org.uk, robh+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: mark.rutland@arm.com, lars@metafoo.de, alexandre.torgue@st.com,
linux-iio@vger.kernel.org, pmeerw@pmeerw.net,
mcoquelin.stm32@gmail.com, knaack.h@gmx.de
Subject: Re: [PATCH 1/2] dt-bindings: iio: stm32-adc: add option to set resolution
Date: Sat, 25 Feb 2017 15:11:59 +0000 [thread overview]
Message-ID: <d64bd76d-a2c6-6148-c126-fa73e96019a1@kernel.org> (raw)
In-Reply-To: <b9f59559-c7a8-f575-0868-bd3b149a35c9@st.com>
On 24/02/17 16:04, Fabrice Gasnier wrote:
> On 02/19/2017 01:09 PM, Jonathan Cameron wrote:
>> On 15/02/17 16:55, Fabrice Gasnier wrote:
>>> Add documentation for 'st,adc-res' dt optional property.
>>>
>>> Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
>> I'm happy with this, but would like to leave time for a device tree review.
>>
>> Ultimately we may well want to make this a generic property and call it something
>> like adc-resolution but perhaps we need to wait until we have a few more devices
>> supporting setting it via device tree to figure out what the best interface is.
>> It would exactly be a problem to support this as a deprecated binding at that
>> point.
>
> Hi Jonathan,
>
> I agree with you on this... It may be better to have generic property
> for this, especially if you see that it will come in the near future.
> May I suggest this prop to be less restrictive, e.g. like
> resolution-bits as is may also be worth for other device types, e.g.
> DAC as an example ?>
Sure, why not - no loss of meaning here. We may never use it for anything
else but that doesn't matter.
>>
>> Give me a poke if we hear nothing from Rob or Mark for say another week.
>
> No news yet, but it can wait a little longer.
Rob / Mark, can you take a look at this if you have time?
Thanks,
Jonathan
>
> Please advise,
> Regards,
> Fabrice
>
>>
>> Thanks,
>>
>> Jonathan
>>
>>> ---
>>> Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
>>> index 5dfc88e..45f7ff2 100644
>>> --- a/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
>>> +++ b/Documentation/devicetree/bindings/iio/adc/st,stm32-adc.txt
>>> @@ -57,6 +57,9 @@ Optional properties:
>>> - dmas: Phandle to dma channel for this ADC instance.
>>> See ../../dma/dma.txt for details.
>>> - dma-names: Must be "rx" when dmas property is being used.
>>> +- st,adc-res: Resolution (bits) to use for conversions. Must match device
>>> + available resolutions (e.g. can be 6, 8, 10 or 12 on stm32f4). Default
>>> + is maximum resolution if unset.
>>>
>>> Example:
>>> adc: adc@40012000 {
>>> @@ -84,6 +87,7 @@ Example:
>>> st,adc-channels = <8>;
>>> dmas = <&dma2 0 0 0x400 0x0>;
>>> dma-names = "rx";
>>> + st,adc-res = <8>;
>>> };
>>> ...
>>> other adc child nodes follow...
>>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-25 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 16:55 [PATCH 0/2] iio: allow to set STM32 ADC resolution Fabrice Gasnier
2017-02-15 16:55 ` [PATCH 1/2] dt-bindings: iio: stm32-adc: add option to set resolution Fabrice Gasnier
2017-02-19 12:09 ` Jonathan Cameron
2017-02-24 16:04 ` Fabrice Gasnier
2017-02-25 15:11 ` Jonathan Cameron [this message]
2017-02-28 8:21 ` Fabrice Gasnier
2017-02-28 8:34 ` Lars-Peter Clausen
2017-02-28 10:14 ` Fabrice Gasnier
[not found] ` <84b7cbab-1342-7f80-cab6-132324e002a4-qxv4g6HH51o@public.gmane.org>
2017-03-05 11:14 ` Jonathan Cameron
2017-02-27 14:29 ` Rob Herring
2017-02-15 16:55 ` [PATCH 2/2] iio: adc: stm32: add dt " Fabrice Gasnier
2017-02-19 12:09 ` Jonathan Cameron
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=d64bd76d-a2c6-6148-c126-fa73e96019a1@kernel.org \
--to=jic23@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@st.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
/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).