From: Jonathan Cameron <jic23@kernel.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [v2 2/8] dt-bindings: iio: adc: Binding ast2600 adc.
Date: Sat, 31 Jul 2021 18:24:29 +0100 [thread overview]
Message-ID: <20210731182334.2be68876@jic23-huawei> (raw)
In-Reply-To: <8D93D26B-AE57-4E38-A1AD-FA62894F2947@aspeedtech.com>
On Mon, 26 Jul 2021 07:21:29 +0000
Billy Tsai <billy_tsai@aspeedtech.com> wrote:
> Hi Jonathan,
>
> Thanks for your review. I will fix them.
> About the vref I reply inline.
>
> On 2021/7/23, 10:52 PM, "Jonathan Cameron" <Jonathan.Cameron@Huawei.com> wrote:
>
> On Fri, 23 Jul 2021 16:16:15 +0800
> Billy Tsai <billy_tsai@aspeedtech.com> wrote:
>
> > > + ? Internal or External reference voltage.
> > > + ? Support 2 Internal reference voltage 1.2v or 2.5v.
> > > + ? Integrate dividing circuit for battery sensing.
> > >
> > > properties:
> > > compatible:
> > > enum:
> > > - aspeed,ast2400-adc
> > > - aspeed,ast2500-adc
> > > + - aspeed,ast2600-adc
> > >
> > > reg:
> > > maxItems: 1
> > > @@ -33,6 +45,18 @@ properties:
> > > "#io-channel-cells":
> > > const: 1
> > >
> > > + vref:
> > > + minItems: 900
> > > + maxItems: 2700
> > > + default: 2500
> > > + description:
> > > + ADC Reference voltage in millivolts.
>
> > I'm not clear from this description. Is this describing an externally
> > connected voltage reference? If so it needs to be done as a regulator.
> > If it's a classic high precision reference, the dts can just use
> > a fixed regulator.
>
> In the ast2600, the ADC supports two internal reference voltages of 1.2v or 2.5v,
> as well as external voltages. When the user selects a voltage of 1.2v or 2.5v, my
> driver will first select to use the internal voltage.
Understood.
> As you mention at patch #4, you suggest to use two property to handle this feature.
> vref: indicate the regulator handler. Like other dt-bindings used.
vref-supply would be the binding but otherwise yes.
> aspeed,int_vref_mv: indicate the chosen of 1.2v or 2.5v
> and use "model_data->vref_fixed" to exclude ast2400 and ast2500
> Is it right?
Ideally you would check in the driver and also use something here
to allow device trees to be checked automatically. Something like
allOf:
- if:
not:
properties:
compatible:
contains: const: aspeed,ast2600-adc
then:
int_vref_mv: false
that will ensure the property is only used for the ast2600.
Note the above is from memory, so may well have incorrect syntax.
I've never found yaml intuitive!
Thanks,
Jonathan
>
> Thanks
>
> > > +
> > > + battery-sensing:
> > > + type: boolean
> > > + description:
> > > + Inform the driver that last channel will be used to sensor battery.
>
> > This isn't (I think?) a standard dt binding, so it needs a manufacturer
> > prefix.
>
> > aspeed,battery-sensing
>
> Best Regards,
> Billy Tsai
>
>
next prev parent reply other threads:[~2021-07-31 17:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 8:16 [v2 0/8] Add support for ast2600 ADC Billy Tsai
2021-07-23 8:16 ` [v2 1/8] dt-bindings: iio: adc: rename the aspeed adc yaml Billy Tsai
2021-07-23 14:44 ` Jonathan Cameron
2021-07-26 6:53 ` Billy Tsai
2021-07-29 20:31 ` Rob Herring
2021-07-31 17:27 ` Jonathan Cameron
2021-07-23 8:16 ` [v2 2/8] dt-bindings: iio: adc: Binding ast2600 adc Billy Tsai
2021-07-23 14:51 ` Jonathan Cameron
2021-07-26 7:21 ` Billy Tsai
2021-07-31 17:24 ` Jonathan Cameron [this message]
2021-07-23 8:16 ` [v2 3/8] iio: adc: aspeed: completes the bitfield declare Billy Tsai
2021-07-23 14:55 ` Jonathan Cameron
2021-07-23 8:16 ` [v2 4/8] iio: adc: aspeed: Allow driver to support ast2600 Billy Tsai
2021-07-23 15:29 ` Jonathan Cameron
2021-07-23 8:16 ` [v2 5/8] iio: adc: aspeed: Add func to set sampling rate Billy Tsai
2021-07-23 15:37 ` Jonathan Cameron
2021-07-23 8:16 ` [v2 6/8] iio: adc: aspeed: Add compensation phase Billy Tsai
2021-07-23 15:44 ` Jonathan Cameron
2021-07-23 8:16 ` [v2 7/8] iio: adc: aspeed: Fix the calculate error of clock Billy Tsai
2021-07-23 8:16 ` [v2 8/8] iio: adc: aspeed: Support battery sensing Billy Tsai
2021-07-23 15:56 ` Jonathan Cameron
2021-07-26 6:54 ` Billy Tsai
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=20210731182334.2be68876@jic23-huawei \
--to=jic23@kernel.org \
--cc=linux-aspeed@lists.ozlabs.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