From: jic23@kernel.org (Jonathan Cameron)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/2] iio: adc: vf610: implement configurable conversion modes
Date: Sun, 14 Jun 2015 12:12:04 +0100 [thread overview]
Message-ID: <557D6184.90105@kernel.org> (raw)
In-Reply-To: <14d469dedae9de1ce519fe90401e526e@agner.ch>
On 08/06/15 21:07, Stefan Agner wrote:
> On 2015-06-08 19:49, Rob Herring wrote:
>> On Wed, May 27, 2015 at 7:47 AM, Stefan Agner <stefan@agner.ch> wrote:
>>> Support configurable conversion mode through sysfs. So far, the
>>> mode used was low-power, which is enabled by default now. Beside
>>> that, the modes normal and high-speed are selectable as well.
>>>
>>> Use the new device tree property which specifies the maximum ADC
>>> conversion clock frequencies. Depending on the mode used, the
>>> available resulting conversion frequency are calculated
>>> dynamically.
>>>
>>> Acked-by: Fugang Duan <B38611@freescale.com>
>>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>>> ---
>>> Documentation/ABI/testing/sysfs-bus-iio-vf610 | 7 +
>>> .../devicetree/bindings/iio/adc/vf610-adc.txt | 9 ++
>>> drivers/iio/adc/vf610_adc.c | 146 +++++++++++++++------
>>> 3 files changed, 120 insertions(+), 42 deletions(-)
>>> create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-vf610
>>>
>>> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-vf610 b/Documentation/ABI/testing/sysfs-bus-iio-vf610
>>> new file mode 100644
>>> index 0000000..ecbc1f4
>>> --- /dev/null
>>> +++ b/Documentation/ABI/testing/sysfs-bus-iio-vf610
>>> @@ -0,0 +1,7 @@
>>> +What: /sys/bus/iio/devices/iio:deviceX/conversion_mode
>>> +KernelVersion: 4.2
>>> +Contact: linux-iio at vger.kernel.org
>>> +Description:
>>> + Specifies the hardware conversion mode used. The three
>>> + available modes are "normal", "high-speed" and "low-power",
>>> + where the last is the default mode.
>>> diff --git a/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt b/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
>>> index 1a4a43d..3eb40e2 100644
>>> --- a/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
>>> +++ b/Documentation/devicetree/bindings/iio/adc/vf610-adc.txt
>>> @@ -11,6 +11,13 @@ Required properties:
>>> - clock-names: Must contain "adc", matching entry in the clocks property.
>>> - vref-supply: The regulator supply ADC reference voltage.
>>>
>>> +Recommended properties:
>>> +- fsl,adck-max-frequency: Maximum frequencies according to datasheets operating
>>> + requirements. Three values are required, depending on conversion mode:
>>> + - Frequency in normal mode (ADLPC=0, ADHSC=0)
>>> + - Frequency in high-speed mode (ADLPC=0, ADHSC=1)
>>> + - Frequency in low-power mode (ADLPC=1, ADHSC=0)
>>
>> Why is this "adck" rather than "adc"?
>
> That is the name of the clock according to the reference manual and data
> sheet.
>
>> How is this related to today's patch adding min-sample-time?
>
> It is related in that this clock is the base to calculate the sampling
> time, but otherwise not really related. Afaik, not respecting the
> maximum clock frequency is probably more a issue for the SAR part of the
> ADC.
Rob, are you happy with Stefan's responses?
>
> --
> Stefan
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-06-14 11:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:47 [PATCH v5 0/2] iio: adc: vf610: respect ADC clocking limitations Stefan Agner
2015-05-27 12:47 ` [PATCH v5 1/2] iio: adc: vf610: implement configurable conversion modes Stefan Agner
2015-06-07 16:54 ` Jonathan Cameron
2015-06-08 17:49 ` Rob Herring
2015-06-08 20:07 ` Stefan Agner
2015-06-14 11:12 ` Jonathan Cameron [this message]
2015-06-23 14:27 ` Rob Herring
2015-05-27 12:47 ` [PATCH v5 2/2] ARM: dts: add property for maximum ADC clock frequencies Stefan Agner
2015-06-07 16:56 ` Jonathan Cameron
2015-06-07 19:23 ` Stefan Agner
2015-08-03 12:22 ` Stefan Agner
2015-08-05 13:46 ` Shawn Guo
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=557D6184.90105@kernel.org \
--to=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).