Re: [PATCH v9 4/4] platform/x86: dell-smo8800: Add support for probing for the accelerometer i2c address

[Andy Shevchenko <andy@kernel.org>]

On Mon, Jan 13, 2025 at 05:17:43PM +0200, Ilpo Järvinen wrote:
> On Sat, 21 Dec 2024, Hans de Goede wrote:
> > On 17-Dec-24 5:48 PM, Ilpo Järvinen wrote:
> > > On Mon, 9 Dec 2024, Hans de Goede wrote:

...

> > > So what was the result of the private inquiry to Dell?
> > 
> > On July 5th I send the following email to Prasanth Ksr
> > <prasanth.ksr@dell.com> which is the only dell.com address I could
> > find in MAINTAINERS other then Dell.Client.Kernel@dell.com which
> > does not seem to be monitored very actively:
> > 
> > """
> > Hello Prasanth,
> > 
> > I'm contacting you about a question lis3lv02d freelfall sensors /
> > accelerometers used on many (older) Dell laptop models. There
> > has been a question about this last December and a patch-set
> > trying to address part of this with Dell.Client.Kernel@dell.com
> > in the Cc but no-one seems to be responding to that email address
> > which is why I'm contacting you directly:
> > 
> > https://lore.kernel.org/linux-i2c/4820e280-9ca4-4d97-9d21-059626161bfc@molgen.mpg.de/
> > https://lore.kernel.org/platform-driver-x86/20240704125643.22946-1-hdegoede@redhat.com/
> > 
> > If you are not the right person to ask these questions to, then
> > please forward this email to the right person.
> > 
> > The lis3lv02d sensors are I2C devices and are described in the ACPI
> > tables with an SMO88xx ACPI device node. The problem is that these
> > ACPI device nodes do not have an ACPI I2cResouce in there resource
> > (_CRS) list, so the I2C address of the sensor is unknown.
> > 
> > When support was first added for these Dell provided a list of
> > model-name to I2C address mappings for the then current generation
> > of laptops, see:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/i2c/busses/i2c-i801.c#n1227
> > 
> > And later the community added a few more mappings.
> > 
> > Paul Menzel, the author of the email starting the discussion on this:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/i2c/busses/i2c-i801.c#n1227
> > 
> > did a search for the kernel message which is printed when an SMO88xx
> > ACPI device is found but the i2c-address is unknown and Paul found
> > many models are missing from the mapping table (see Paul's email).
> > 
> > Which leads us to the following questions:
> > 
> > 1. Is there another, uniform (so not using a model name table)
> > way to find out the I2C address of the SMO88xx freefall sensor
> > from the ACPI or SMBIOS tables ?
> > 
> > 2. If we need to keep using the model-name to I2C-address mapping
> > table can you help us complete it by providing the sensor's I2C
> > address for all models Paul has found where this is currently missing ?
> > 
> > Regards,
> > 
> > Hans
> > """
> > 
> > Pali and Paul Menzel where in the Cc of this email.
> > 
> > > Did they respond?
> > 
> > I got a reply from Prasanth that they would forward my request to the
> > correct team. Then I got on off-list reply to the v6 patch-set from
> > David Wang from Dell with as relevant content "We are working on it."
> > 
> > > Did they provide useful info?
> > 
> > No further info was received after the "We are working on it." email.
> 
> Hi Hans,
> 
> So you didn't try to remind them after that at all?
> 
> This kind of sounds a low priority item they just forgot to do and might have
> had an intention to follow through.

Talking from my experience with other companies that could have done something
better I dare to say that this entire buzz for them is no-priority at all, like
"no money stuff", hence no attention given. That said, I believe ping won't
change anything here, however I agree that it _was_ worth to try to acquire any
response from them.

Just my 2c.

-- 
With Best Regards,
Andy Shevchenko