From: William Breathitt Gray <william.gray@linaro.org>
To: jic23@kernel.org
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org,
William Breathitt Gray <william.gray@linaro.org>
Subject: [PATCH 0/2] iio: Implement and utilize register structures for
Date: Mon, 6 Jun 2022 10:15:16 -0400 [thread overview]
Message-ID: <cover.1654118389.git.william.gray@linaro.org> (raw)
The STX104 and CIO-DAC drivers were updated to use I/O memory accessor
calls such as ioread8()/iowrite8() in previous patch series [1]. This
patch series is a continuation of the effort to improve the code
readability and reduce magic numbers by implementing and utilizing named
register data structures.
[1] https://lore.kernel.org/all/cover.1652201921.git.william.gray@linaro.org/
William Breathitt Gray (2):
iio: adc: stx104: Implement and utilize register structures
iio: dac: cio-dac: Implement and utilize register structures
drivers/iio/adc/stx104.c | 70 ++++++++++++++++++++++++++-------------
drivers/iio/dac/cio-dac.c | 24 +++++++++-----
2 files changed, 63 insertions(+), 31 deletions(-)
base-commit: 7fa61f7dba74f6c5baf9f02b760924692acdd282
--
2.36.1
next reply other threads:[~2022-06-06 14:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 14:15 William Breathitt Gray [this message]
2022-06-06 14:15 ` [PATCH 1/2] iio: adc: stx104: Implement and utilize register structures William Breathitt Gray
2022-06-14 11:22 ` Jonathan Cameron
2022-06-14 16:12 ` William Breathitt Gray
2022-06-15 9:44 ` Andy Shevchenko
2022-06-15 11:55 ` William Breathitt Gray
2022-06-15 12:00 ` Andy Shevchenko
2022-06-15 12:19 ` William Breathitt Gray
2022-06-15 12:43 ` Andy Shevchenko
2022-06-16 13:27 ` Mark Brown
2022-06-06 14:15 ` [PATCH 2/2] iio: dac: cio-dac: " William Breathitt Gray
2022-06-14 11:26 ` Jonathan Cameron
2022-06-14 16:15 ` William Breathitt Gray
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=cover.1654118389.git.william.gray@linaro.org \
--to=william.gray@linaro.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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