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: Fri, 15 Nov 2024 07:46:23 -0800	[thread overview]
Message-ID: <6344faca-d312-48c1-91a3-7b2b80f4a529@roeck-us.net> (raw)
In-Reply-To: <ZzdjWWrTK1bniwFf@finisterre.sirena.org.uk>

On 11/15/24 07:06, Mark Brown wrote:
> On Thu, Nov 14, 2024 at 10:58:05PM -0800, Guenter Roeck wrote:
>> On Thu, Nov 14, 2024 at 05:26:19PM +0000, Mark Brown wrote:
> 
>>> Right, so the fact that I3C depends on I2C deals with a lot of the
>>> problems that plague the I2C/SPI combination.  Ugh.  I guess the helper
>>> should be OK and there's not much doing for I2C/SPI.
> 
>> Is it really that difficult for I2C and SPI ? The patch below seems to work
>> for the LTC2947 driver. It doesn't even need dummies (the compiler drops
>> the unused code), though I am not sure if that can be relied on. I thought
>> that dummy functions are needed, but maybe I am wrong.
>>
>> The Kconfig for the combined ltc2947 driver is
>>
>> config SENSORS_LTC2947
>>          tristate "Analog Devices LTC2947 High Precision Power and Energy Monitor"
>>          depends on I2C || SPI
>>          depends on I2C || I2C=n
>>          select REGMAP_I2C if I2C
>>          select REGMAP_SPI if SPI
> 
> This prevents building the driver in if I2C=m which isn't always
> desirable, and IIRC the randconfig people kept turning issues up.  You
> can make things work well enough for normal configurations, it's all
> edge cases that cause issues.

You mean if SPI=y and I2C=m ? Good point. That isn't normally a problem
for sensor drivers, but I understand that it may be undesirable for others.

Thanks,
Guenter


  reply	other threads:[~2024-11-15 15:46 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
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 [this message]
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=6344faca-d312-48c1-91a3-7b2b80f4a529@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®