mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Frank Li <Frank.Li@nxp.com>
Subject: Re: regmap I3C support
Date: Thu, 14 Nov 2024 06:45:52 -0800	[thread overview]
Message-ID: <85584c2e-2c45-4ec4-89a0-111fa5ad1080@roeck-us.net> (raw)
In-Reply-To: <ZzXfmonkRB-KaBhi@finisterre.sirena.org.uk>

On 11/14/24 03:31, Mark Brown wrote:
> On Wed, Nov 13, 2024 at 12:16:37PM -0800, Guenter Roeck wrote:
>> On 11/13/24 06:41, Mark Brown wrote:
> 
>>> That's kind of my question.  If we are going to have this sort of stuff
>>> we should also have it for I2C and SPI since it's such a common pattern.
> 
>> I'll take that as "we are not going to provide a dummy regmap i3c registration
>> function". Thanks, that is all I needed to know.
> 
> It's not a definite no, it's a "is this just going to run into the same
> problems we ran into with I2C and SPI and never get used?" or
> alternatively "have people figured out a better solution to the problems
> we had with I2C and SPI which we can adopt there?" - it's something we
> wanted to do before but ran into trouble with.

We now use

config SENSORS_TMP108
         tristate "Texas Instruments TMP108"
         depends on I2C
         depends on I3C || !I3C
         select REGMAP_I2C
         select REGMAP_I3C if I3C

and in the i3c_probe function

#ifdef CONFIG_REGMAP_I3C
         regmap = devm_regmap_init_i3c(i3cdev, &tmp108_regmap_config);
#else
         regmap = ERR_PTR(-ENODEV);
#endif
         if (IS_ERR(regmap))

Clumsy, and not my preferred solution, but it works.

Guenter


  reply	other threads:[~2024-11-14 14:45 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
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 [this message]
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=85584c2e-2c45-4ec4-89a0-111fa5ad1080@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=Frank.Li@nxp.com \
    --cc=broonie@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

all inboxes | Powered by JetHome®