From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Li <Frank.Li@nxp.com>
Subject: Re: regmap I3C support
Date: Wed, 13 Nov 2024 14:01:13 +0000 [thread overview]
Message-ID: <ZzSxKctLlLZexdF5@finisterre.sirena.org.uk> (raw)
In-Reply-To: <67d549d0-64c6-4d62-add6-0958ef24910f@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Mon, Nov 11, 2024 at 11:07:40AM -0800, Guenter Roeck wrote:
> For simpler I2C / I3C devices, there is module_i3c_i2c_driver() which is
> supposed to register both the I2C and the I3C drivers and handle the situation
> where I3C is not enabled.
> That works fine unless the driver uses regmap, but I3C and with it REGMAP_I3C
> is not enabled. There is no dummy function for devm_regmap_init_i3c(), so
> a probe function for an I2C/I3C driver utilizing regmap can not be built
> unless REGMAP_I3C and with it I3C is enabled. Ultimately that means that
> I2C/I3C drivers using regmap can not use module_i3c_i2c_driver() to register
> the driver.
> Am I missing something ? Otherwise, would it be possible to consider
> a dummy devm_regmap_init_i3c() function if REGMAP_I3C=n ?
Don't these drivers end up with the same miserable problems with
dependencies on variations of things being configured built in and
modules anyway that mean we build separate SPI and I2C bus wrappers for
the same case with devices that do both I2C and SPI?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-11-13 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 19:07 Guenter Roeck
2024-11-13 14:01 ` Mark Brown [this message]
2024-11-13 14:15 ` Guenter Roeck
2024-11-13 14:41 ` Mark Brown
2024-11-13 20:16 ` Guenter Roeck
2024-11-14 11:31 ` Mark Brown
2024-11-14 14:45 ` Guenter Roeck
2024-11-14 17:26 ` Mark Brown
2024-11-15 6:58 ` Guenter Roeck
2024-11-15 15:06 ` Mark Brown
2024-11-15 15:46 ` Guenter Roeck
2024-11-16 4:35 ` Guenter Roeck
2024-11-19 17:46 ` Mark Brown
2024-11-19 18:41 ` Guenter Roeck
2024-11-19 19:30 ` Frank Li
2024-11-19 21:57 ` Guenter Roeck
2024-11-19 22:22 ` Frank Li
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=ZzSxKctLlLZexdF5@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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
all inboxes | Powered by JetHome®