From: <Eugen.Hristev@microchip.com>
To: <jic23@kernel.org>, <linux-iio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <Ludovic.Desroches@microchip.com>,
<alexandru.ardelean@analog.com>, <Eugen.Hristev@microchip.com>
Subject: [PATCH v3 0/3] Enhancements to at91-sama5d2_adc driver
Date: Tue, 28 Jan 2020 12:57:38 +0000 [thread overview]
Message-ID: <1580216189-27418-1-git-send-email-eugen.hristev@microchip.com> (raw)
From: Eugen Hristev <eugen.hristev@microchip.com>
This is a rework of the first patches from
[PATCH 00/10] Enhancements to at91-sama5d2_adc and rtc trigger
I reworked according to Jonathan's review.
The RTC triggering part is still work in progress and I will send it separately
Changes in v3:
- Addressed feedback (each patch has changelog) from Jonathan on ML on the v2
of this series:
[PATCH v2 0/3] Enhancements to at91-sama5d2_adc driver
Eugen Hristev (3):
iio: adc: at91-sama5d2_adc: fix differential channels in triggered
mode
iio: adc: at91-sama5d2_adc: handle unfinished conversions
iio: adc: at91-sama5d2_adc: update for other trigger usage
drivers/iio/adc/at91-sama5d2_adc.c | 167 ++++++++++++++++++++++++-------------
1 file changed, 109 insertions(+), 58 deletions(-)
--
2.7.4
next reply other threads:[~2020-01-28 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 12:57 Eugen.Hristev [this message]
2020-01-28 12:57 ` [PATCH v3 1/3] iio: adc: at91-sama5d2_adc: fix differential channels in triggered mode Eugen.Hristev
2020-02-02 11:02 ` Jonathan Cameron
2020-03-23 10:42 ` Eugen.Hristev
2020-03-28 17:31 ` Jonathan Cameron
2020-01-28 12:57 ` [PATCH v3 2/3] iio: adc: at91-sama5d2_adc: handle unfinished conversions Eugen.Hristev
2020-04-25 14:52 ` Jonathan Cameron
2020-01-28 12:57 ` [PATCH v3 3/3] iio: adc: at91-sama5d2_adc: update for other trigger usage Eugen.Hristev
2020-02-02 11:05 ` 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=1580216189-27418-1-git-send-email-eugen.hristev@microchip.com \
--to=eugen.hristev@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=alexandru.ardelean@analog.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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
Powered by JetHome