From: Gene Chen <gene.chen.richtek@gmail.com>
To: jic23@kernel.org, robh+dt@kernel.org, matthias.bgg@gmail.com
Cc: gene_chen@richtek.com, devicetree@vger.kernel.org,
lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, cy_huang@richtek.com,
benjamin.chao@mediatek.com, linux-mediatek@lists.infradead.org,
pmeerw@pmeerw.net, knaack.h@gmx.de, Wilma.Wu@mediatek.com,
linux-arm-kernel@lists.infradead.org, shufan_lee@richtek.com
Subject: [PATCH v6 0/3] iio: adc: mt6360: Add ADC driver for MT6360
Date: Thu, 1 Oct 2020 16:54:05 +0800 [thread overview]
Message-ID: <1601542448-7433-1-git-send-email-gene.chen.richtek@gmail.com> (raw)
This patch series add MT6360 ADC support contains driver, testing document
and binding document
Gene Chen (2)
dt-bindings: iio: adc: add bindings doc for MT6360 ADC
Documentation: ABI: testing: mt6360: Add ADC sysfs guideline
iio: adc: mt6360: Add ADC driver for MT6360
Documentation/ABI/testing/sysfs-bus-iio-adc-mt6360 | 78 ++
Documentation/devicetree/bindings/iio/adc/mediatek,mt6360-adc.yaml | 34
drivers/iio/adc/Kconfig | 11
drivers/iio/adc/Makefile | 1
drivers/iio/adc/mt6360-adc.c | 362 ++++++++++
5 files changed, 486 insertions(+)
changelogs between v1 & v2
- adc: use IIO_CHAN_INFO_PROCESSED only
- adc: use devm_iio_triggered_buffer_setup
- adc: use use s64 to record timestamp
changelogs between v2 & v3
- Rearrange include file order by alphabet
- Set line length constraint below 100
- Add Document for testing adc sysfs node guideline
- Set compiler 64 bit aligned when handle iio timestamp
changelogs between v3 & v4
- Fix sysfs guideline description
- Replace iio channel processed by raw/scale/offset
- Add comment of read adc flow for special HW design
changelogs between v4 & v5
- Rename dt-bindings aligned to file name
- Aligned sysfs node name with driver and add VBUSDIVX description
- Add ADC channel sysfs node "*_labels"
changelogs between v5 & v6
- Memset aligned adc data
- Remove strong casting void pointer
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-09-30 8:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 8:54 Gene Chen [this message]
2020-10-01 8:54 ` [PATCH v6 1/3] dt-bindings: iio: adc: add bindings doc for MT6360 ADC Gene Chen
2020-10-05 14:38 ` Rob Herring
2020-10-01 8:54 ` [PATCH v6 2/3] Documentation: ABI: testing: mt6360: Add ADC sysfs guideline Gene Chen
2020-10-01 8:54 ` [PATCH v6 3/3] iio: adc: mt6360: Add ADC driver for MT6360 Gene Chen
2020-09-30 11:12 ` kernel test robot
2020-10-16 15:28 ` Andy Shevchenko
2020-10-10 16:57 ` [PATCH v6 0/3] " 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=1601542448-7433-1-git-send-email-gene.chen.richtek@gmail.com \
--to=gene.chen.richtek@gmail.com \
--cc=Wilma.Wu@mediatek.com \
--cc=benjamin.chao@mediatek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=gene_chen@richtek.com \
--cc=jic23@kernel.org \
--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-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@kernel.org \
--cc=shufan_lee@richtek.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).