Linux I2C development
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "Jean Delvare" <jdelvare@suse.com>,
	"Andi Shyti" <andi.shyti@kernel.org>,
	"Wolfram Sang" <wsa@the-dreams.de>,
	"Patrick Höhn" <hoehnp@gmx.de>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH RFT] i2c: i801: Scan for Dell accelerometer i2c address
Date: Fri, 3 May 2024 16:39:39 +0200	[thread overview]
Message-ID: <20240503143939.xfsxwrcmiflty5fl@pali> (raw)
In-Reply-To: <cb2e65f8-066a-41ea-ae3b-03950714f33c@gmail.com>

On Friday 03 May 2024 16:09:03 Heiner Kallweit wrote:
> So far each new Dell device with an accelerometer requires a patch.
> All devices, with one older system as an exception, use address 0x29.
> So I think we can safely scan for the correct address

This is too risky. Poking random smbus address can lead to the lockup or
crash of the whole system. I really dislike such change which is going
to unconditionally on every system to scan or access fixed smbus address.
Crashing kernel on some new model in future or on some older models is
the worst user experience which can happen.

The hardcoded table with model name and address is the safest option to
prevent crashes or other unexpected behavior.

Instead, I would suggest to contact Dell if they can provide a way to
read accelerometer's i2c/smbus address from ACPI/WMI/DMI. And if there
is not any way right now then ask Dell to include it for new products.
So we can avoid having hardcoded table for new products released in
future.

  reply	other threads:[~2024-05-03 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 14:09 [PATCH RFT] i2c: i801: Scan for Dell accelerometer i2c address Heiner Kallweit
2024-05-03 14:39 ` Pali Rohár [this message]
2024-05-03 20:43   ` Heiner Kallweit

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=20240503143939.xfsxwrcmiflty5fl@pali \
    --to=pali@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=hoehnp@gmx.de \
    --cc=jdelvare@suse.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa@the-dreams.de \
    /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