Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Gwendal Grignou <gwendal@chromium.org>, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: proximity: sx_common: Add old register mapping
Date: Fri, 10 Feb 2023 17:17:20 +0000	[thread overview]
Message-ID: <20230210171720.30ef1be9@jic23-huawei> (raw)
In-Reply-To: <20230205145759.2ce9f274@jic23-huawei>

On Sun, 5 Feb 2023 14:57:59 +0000
Jonathan Cameron <jic23@kernel.org> wrote:

> On Mon, 30 Jan 2023 11:41:31 -0800
> Stephen Boyd <swboyd@chromium.org> wrote:
> 
> > Quoting Gwendal Grignou (2023-01-28 16:37:53)  
> > > Older firmwares still send sensor configuration using a list of
> > > registers with opaque values defined during sensor tuning.
> > > sx9234 and sx9360 sensor on ACPI based devices are concerned.
> > > More schema to configure the sensors will be needed to support devices
> > > designed for windows, like Samsung Galaxy Book2.
> > >
> > > Support schema is: "<_HID>.<register_name>". For instance
> > > "STH9324,reg_adv_ctrl2" in:
> > >
> > >     Scope (\_SB.PCI0.I2C2)
> > >     {
> > >         Device (SX28)
> > >         {
> > >             Name (_HID, "STH9324")  // _HID: Hardware ID
> > > ...
> > >             Name (_DSD, Package (0x02)  // _DSD: Device-Specific Data
> > >             {
> > >                 ToUUID ("daffd814-6eba-4d8c-8a91-bc9bbf4aa301") /*
> > > Device Properties for _DSD */,
> > >                 Package (0x3F)
> > >                 {
> > > ...
> > >                     Package (0x02)
> > >                     {
> > >                         "STH9324,reg_adv_ctrl2",
> > >                         Zero
> > >                     },`
> > >
> > > Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
> > > ---    
> > 
> > Reviewed-by: Stephen Boyd <swboyd@chromium.org>  
> Applied to the togreg branch of iio.git and pushed out as testing.
> 
> Timing wise, we are late in the cycle so this might not make it upstream
> until next cycle.
> 

Dropped for now as we need to fix an issue with acpi_device_hid()
not being defined with !CONFIG_ACPI that broke some builds in next.

Jonathan


> Thanks,
> 
> Jonathan
> 


  reply	other threads:[~2023-02-10 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-29  0:37 [PATCH v3] iio: proximity: sx_common: Add old register mapping Gwendal Grignou
2023-01-30 19:41 ` Stephen Boyd
2023-02-05 14:57   ` Jonathan Cameron
2023-02-10 17:17     ` Jonathan Cameron [this message]
2023-02-11  0:25       ` Gwendal Grignou

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=20230210171720.30ef1be9@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=gwendal@chromium.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=swboyd@chromium.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