From: Gabriel Braga Lagrotaria <gabrielblo@ime.usp.br>
To: andy@kernel.org, dlechner@baylibre.com,
javier.carrasco.cruz@gmail.com, jic23@kernel.org,
nuno.sa@analog.com
Cc: ricardo.kojo@ime.usp.br, elliancarlos@gmail.com,
linux-iio@vger.kernel.org
Subject: [PATCH v2 0/2] iio: light: veml6030: Generalize hw_init and cleanup naming
Date: Sat, 2 May 2026 20:41:02 -0300 [thread overview]
Message-ID: <20260502234348.131563-1-gabrielblo@ime.usp.br> (raw)
Hello,
This patchset refactors the veml6030 driver to improve support for device
variations and future-proof the codebase. The primary focus is to
deduplicate the hardware initialization logic and move away from wildcard
naming conventions.
The first patch removes the 'x' wildcard from the main chip structure,
renaming it to 'veml6030_chip_desc'. The second patch introduces a
configuration structure to handle device-specific values, allowing
veml6030 and veml6035 to share a single initialization path.
Changes in v2:
- Renamed 'struct veml603x_chip' to 'struct veml6030_chip_desc' to
avoid wildcard naming as requested.
- Refactored initialization logic to use a configuration descriptor,
removing the redundant veml6035_hw_init().
Gabriel Braga Lagrotaria (2):
iio: light: veml6030: Remove 'x' wildcard usages in file
iio: light: veml6030: Generalize hw_init for veml6030 and veml6035
drivers/iio/light/veml6030.c | 102 +++++++++++++++--------------------
1 file changed, 42 insertions(+), 60 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-02 23:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 23:41 Gabriel Braga Lagrotaria [this message]
2026-05-02 23:41 ` [PATCH v2 1/2] iio: light: veml6030: Remove 'x' wildcard usages in file Gabriel Braga Lagrotaria
2026-05-03 9:23 ` Joshua Crofts
2026-05-02 23:41 ` [PATCH v2 2/2] iio: light: veml6030: Generalize hw_init for veml6030 and veml6035 Gabriel Braga Lagrotaria
2026-05-03 0:02 ` Maxwell Doose
2026-05-04 14:14 ` Andy Shevchenko
2026-05-04 16:28 ` Jonathan Cameron
2026-05-04 16:35 ` 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=20260502234348.131563-1-gabrielblo@ime.usp.br \
--to=gabrielblo@ime.usp.br \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=elliancarlos@gmail.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ricardo.kojo@ime.usp.br \
/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