From: William Breathitt Gray <william.gray@linaro.org>
To: jic23@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
William Breathitt Gray <william.gray@linaro.org>,
Fred Eckert <Frede@cmslaser.com>
Subject: [PATCH v2 0/2] iio: Implement and utilize register structures for ISA drivers
Date: Thu, 7 Jul 2022 13:21:23 -0400 [thread overview]
Message-ID: <cover.1657213745.git.william.gray@linaro.org> (raw)
Changes in v2:
- Rename 'ad' member to 'ssr_ad' to indicate access to Software Strobe
Register as well; relevant comments updated
- Dereference DAC channel address via array subscripts in the
stx104_write_raw() function in order to match rest of code
- Replace struct cio_dac_reg with direct u16 pointer to the DAC
address; this greatly simplifies the cio-dac patch
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: Cleanup indexing for DAC writes
drivers/iio/adc/stx104.c | 74 ++++++++++++++++++++++++++-------------
drivers/iio/dac/cio-dac.c | 10 +++---
2 files changed, 55 insertions(+), 29 deletions(-)
base-commit: 338222d8e1121bcb78a86fb39982eddcc367a5bc
--
2.36.1
next reply other threads:[~2022-07-07 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 17:21 William Breathitt Gray [this message]
2022-07-07 17:21 ` [PATCH v2 1/2] iio: adc: stx104: Implement and utilize register structures William Breathitt Gray
2022-07-07 17:21 ` [PATCH v2 2/2] iio: dac: cio-dac: Cleanup indexing for DAC writes William Breathitt Gray
2022-07-16 17:48 ` [PATCH v2 0/2] iio: Implement and utilize register structures for ISA drivers 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=cover.1657213745.git.william.gray@linaro.org \
--to=william.gray@linaro.org \
--cc=Frede@cmslaser.com \
--cc=jic23@kernel.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