From: Angel Iglesias <ang.iglesiasg@gmail.com>
To: linux-iio@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Angel Iglesias <ang.iglesiasg@gmail.com>,
Wolfram Sang <wsa@kernel.org>,
linux-i2c@vger.kernel.org
Subject: [PATCH v2 0/2] i2c: core: Introduce i2c_client_get_device_id helper
Date: Sun, 6 Nov 2022 17:41:49 +0100 [thread overview]
Message-ID: <cover.1667750698.git.ang.iglesiasg@gmail.com> (raw)
Introduces a new i2c helper to query driver match tables and recover the
identity of the bound device. This helper should help with the migration
of existing drivers to use the new i2c_driver .probe_new callback, which
does not provide the device id with the pointer to the driver data as the
previous .probe callback.
As part of the patchset, migrated the bmp280 IIO driver to .new_probe
callback using the new helper.
Changes from v1 --> v2:
* Add further clarification that the device queried needs to be bound to
the driver.
* Drops extra newline after function return.
* Discard unrelated style changes.
Previous version:
https://lore.kernel.org/all/cover.1667151588.git.ang.iglesiasg@gmail.com/
Angel Iglesias (2):
i2c: core: Introduce i2c_client_get_device_id helper function
iio: pressure: bmp280: convert to i2c's .probe_new()
drivers/i2c/i2c-core-base.c | 15 +++++++++++++++
drivers/iio/pressure/bmp280-i2c.c | 6 +++---
include/linux/i2c.h | 1 +
3 files changed, 19 insertions(+), 3 deletions(-)
base-commit: e38fb57870172ed920c206e8d73e2639d83c8847
--
2.38.1
next reply other threads:[~2022-11-06 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 16:41 Angel Iglesias [this message]
2022-11-06 16:42 ` [PATCH v2 1/2] i2c: core: Introduce i2c_client_get_device_id helper function Angel Iglesias
2022-11-06 17:22 ` Jonathan Cameron
2022-11-06 17:50 ` Angel Iglesias
2022-11-06 16:43 ` [PATCH v2 2/2] iio: pressure: bmp280: convert to i2c's .probe_new() Angel Iglesias
2022-11-06 17:25 ` 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.1667750698.git.ang.iglesiasg@gmail.com \
--to=ang.iglesiasg@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.