From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 0/2] Meson8b support for the meson_saradc driver
Date: Sat, 25 Mar 2017 17:29:36 +0100 [thread overview]
Message-ID: <20170325162938.28659-1-martin.blumenstingl@googlemail.com> (raw)
The SAR ADC register layout seems to be mostly the same on older SoCs.
Thus basically all functionality is already supported by the existing
driver.
There are two small differences though:
- the adc_clk and adc_div clock are not provided by the clock-controller
on Meson8b. instead the SAR ADC provides an internal "adc_clk" (this
behavior is already supported by the driver and requires no changes)
- the newer SoCs are using some register bits only the kernel or the
BL30 (bootloader) are using the SAR ADC. This is the main change of
this series: guarding all BL30 specific code with a corresponding
"if"-block.
This also adds a new DT binding for the SAR ADC in Meson8b because the
driver has to specify (for this older version) that there's no BL30
integration available (and these register bits should not be touched).
Martin Blumenstingl (2):
Documentation: dt-bindings: add a Meson8b compatible to the SAR ADC
iio: adc: meson-saradc: add Meson8b SoC compatibility
.../bindings/iio/adc/amlogic,meson-saradc.txt | 1 +
drivers/iio/adc/meson_saradc.c | 70 ++++++++++++++--------
2 files changed, 47 insertions(+), 24 deletions(-)
--
2.12.1
next reply other threads:[~2017-03-25 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 16:29 Martin Blumenstingl [this message]
2017-03-25 16:29 ` [PATCH 1/2] Documentation: dt-bindings: add a Meson8b compatible to the SAR ADC Martin Blumenstingl
2017-03-30 22:47 ` Rob Herring
2017-03-25 16:29 ` [PATCH 2/2] iio: adc: meson-saradc: add Meson8b SoC compatibility Martin Blumenstingl
2017-03-25 16:45 ` Peter Meerwald-Stadler
2017-03-25 18:13 ` Jonathan Cameron
2017-03-25 18:28 ` Martin Blumenstingl
2017-03-25 18:31 ` 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=20170325162938.28659-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=linus-amlogic@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
all inboxes | Powered by JetHome®