public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Nam Cao <namcaov@gmail.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Jean Delvare <jdelvare@suse.de>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: add lis3lv02d's I2C address for Vostro 5568
Date: Wed, 19 Oct 2022 22:34:03 +0200	[thread overview]
Message-ID: <20221019203403.GA149239@nam-dell> (raw)
In-Reply-To: <20221018180051.236tz4yxsdzrgguq@pali>

On Tue, Oct 18, 2022 at 08:00:51PM +0200, Pali Rohár wrote:
> On Tuesday 18 October 2022 19:39:51 Jean Delvare wrote:
> > On Thu, 06 Oct 2022 16:54:40 +0200, Nam Cao wrote:
> > > Dell Vostro 5568 laptop has lis3lv02d, but its i2c address is not known
> > > to the kernel. Add this address.
> > > 
> > > Output of "cat /sys/devices/platform/lis3lv02d/position" on Dell Vostro
> > > 5568 laptop:
> > >     - Horizontal: (-18,0,1044)
> > >     - Front elevated: (522,-18,1080)
> > >     - Left elevated: (-18,-360,1080)
> > >     - Upside down: (36,108,-1134)
> > > 
> > > Signed-off-by: Nam Cao <namcaov@gmail.com>
> > > ---
> > >  drivers/i2c/busses/i2c-i801.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/i2c/busses/i2c-i801.c b/drivers/i2c/busses/i2c-i801.c
> > > index a176296f4fff..e46561e095c6 100644
> > > --- a/drivers/i2c/busses/i2c-i801.c
> > > +++ b/drivers/i2c/busses/i2c-i801.c
> > > @@ -1243,6 +1243,7 @@ static const struct {
> > >  	 */
> > >  	{ "Latitude 5480",      0x29 },
> > >  	{ "Vostro V131",        0x1d },
> > > +	{ "Vostro 5568",        0x29 },
> > >  };
> > >  
> > >  static void register_dell_lis3lv02d_i2c_device(struct i801_priv *priv)
> > 
> > Fine with me.
> > 
> > Reviewed-by: Jean Delvare <jdelvare@suse.de>
> > 
> > Pali, OK with you?
> 
> Yes, nice to see that other people discovered another hidden hardware
> devices in their own laptops :-)
> 
> Reviewed-by: Pali Rohár <pali@kernel.org>
> 
> 
> Nam Cao, could you check your ACPI DSDT table if there is not specified
> this smbus/i2c address 0x29? Autodiscovery would be better than
> hardcoding. At least for E6440 I was told that BIOS does not provide it.

My reply got rejected by mailing list because the attachment was too big.
So I re-send this without the attachment, so that everyone can see.

I searched the DSDT table for "29", but none of them looks like an i2c
address.

But this is the first time I hear about ACPI DSDT table, so I may did
something incorrectly. I did:
        - cp /sys/firmware/acpi/tables/DSDT table
        - iasl -d table
        - Search through table.dsl

Best regards,
Nam

  reply	other threads:[~2022-10-19 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 14:54 [PATCH] i2c: i801: add lis3lv02d's I2C address for Vostro 5568 Nam Cao
2022-10-18 17:39 ` Jean Delvare
2022-10-18 18:00   ` Pali Rohár
2022-10-19 20:34     ` Nam Cao [this message]
2022-10-19 20:52       ` Pali Rohár
2022-11-01 12:46 ` Wolfram Sang

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=20221019203403.GA149239@nam-dell \
    --to=namcaov@gmail.com \
    --cc=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali@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