Created attachment 307036 [details]
dmesg output

Created attachment 307037 [details]
lspci output

On Tue, 22 Oct 2024 13:17:20 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219418
> 
>             Bug ID: 219418
>            Summary: BOSC0200 Accelerometer Invalid chip 12 initialization
>                     error
>            Product: Drivers
>            Version: 2.5
>           Hardware: All
>                 OS: Linux
>             Status: NEW
>           Severity: normal
>           Priority: P3
>          Component: IIO
>           Assignee: drivers_iio@kernel-bugs.kernel.org
>           Reporter: cameraphone77@gmail.com
>         Regression: No
> 
> Created attachment 307035 [details]
>   --> https://bugzilla.kernel.org/attachment.cgi?id=307035&action=edit  
> lspci output
> 
> Hardware: Acer aspire spin 3 A3SP14-31PT-38YA
> 
> One line summary of the problem:
> BOSC0200 Accelerometer Invalid chip 12 initialization error

Unfortunately that ID is used by the windows Bosch drivers for numerous
completely incompatible devices.  So we can't do soft matching on this one.
We need to know what the device actually is and add explicit support for
it.

So it's going to take some detective work to find a device with ID 12.

Any other information on what device this might be?

Jonathan
> 
> Full description of the problem/report:
> The Accelerometer is not detected by iio and does not function
> 
> Kernel version (from /proc/version):
> Linux version 6.11.4-arch2-1 (linux@archlinux) (gcc (GCC) 14.2.1 20240910,
> GNU
> ld (GNU Binutils) 2.43.0) #1 SMP PREEMPT_DYNAMIC Sun, 20 Oct 2024 18:20:12
> +0000
> 
> 
> sudo /usr/lib/iio-sensor-proxy -v
> ** (iio-sensor-proxy:2007): DEBUG: 22:33:10.952: Starting iio-sensor-proxy
> version 3.5
> (iio-sensor-proxy:2007): GLib-GIO-DEBUG: 22:33:10.954: Using cross-namespace
> EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
> ** (iio-sensor-proxy:2007): DEBUG: 22:33:10.991: No sensors or missing kernel
> drivers for the sensors
>

(In reply to Jonathan Cameron from comment #3)
> On Tue, 22 Oct 2024 13:17:20 +0000
> bugzilla-daemon@kernel.org wrote:
> 
> > https://bugzilla.kernel.org/show_bug.cgi?id=219418
> > 
> >             Bug ID: 219418
> >            Summary: BOSC0200 Accelerometer Invalid chip 12 initialization
> >                     error
> >            Product: Drivers
> >            Version: 2.5
> >           Hardware: All
> >                 OS: Linux
> >             Status: NEW
> >           Severity: normal
> >           Priority: P3
> >          Component: IIO
> >           Assignee: drivers_iio@kernel-bugs.kernel.org
> >           Reporter: cameraphone77@gmail.com
> >         Regression: No
> > 
> > Created attachment 307035 [details]
> >   --> https://bugzilla.kernel.org/attachment.cgi?id=307035&action=edit  
> > lspci output
> > 
> > Hardware: Acer aspire spin 3 A3SP14-31PT-38YA
> > 
> > One line summary of the problem:
> > BOSC0200 Accelerometer Invalid chip 12 initialization error
> 
> Unfortunately that ID is used by the windows Bosch drivers for numerous
> completely incompatible devices.  So we can't do soft matching on this one.
> We need to know what the device actually is and add explicit support for
> it.
> 
> So it's going to take some detective work to find a device with ID 12.
> 
> Any other information on what device this might be?
> 
> Jonathan

I looked through all the bosch accelerator datasheets I could find and the closest i could get was:

CHIP     chip_id
BMA423 - 0x13
BMA456 - 0x16

I'm thinking it may be the BMA422 but that datasheet isn't available for some reason.   I did also ask in their forums but no responses.  Unfortunately, I don't think it's an easy task to disassemble the screen.

On Sat, 26 Oct 2024 17:06:36 +0000
bugzilla-daemon@kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219418
> 
> --- Comment #4 from Camera Phone (cameraphone77@gmail.com) ---
> (In reply to Jonathan Cameron from comment #3)
> > On Tue, 22 Oct 2024 13:17:20 +0000
> > bugzilla-daemon@kernel.org wrote:
> >   
> > > https://bugzilla.kernel.org/show_bug.cgi?id=219418
> > > 
> > >             Bug ID: 219418
> > >            Summary: BOSC0200 Accelerometer Invalid chip 12 initialization
> > >                     error
> > >            Product: Drivers
> > >            Version: 2.5
> > >           Hardware: All
> > >                 OS: Linux
> > >             Status: NEW
> > >           Severity: normal
> > >           Priority: P3
> > >          Component: IIO
> > >           Assignee: drivers_iio@kernel-bugs.kernel.org
> > >           Reporter: cameraphone77@gmail.com
> > >         Regression: No
> > > 
> > > Created attachment 307035 [details]  
> > >   --> https://bugzilla.kernel.org/attachment.cgi?id=307035&action=edit    
> > > lspci output
> > > 
> > > Hardware: Acer aspire spin 3 A3SP14-31PT-38YA
> > > 
> > > One line summary of the problem:
> > > BOSC0200 Accelerometer Invalid chip 12 initialization error  
> > 
> > Unfortunately that ID is used by the windows Bosch drivers for numerous
> > completely incompatible devices.  So we can't do soft matching on this one.
> > We need to know what the device actually is and add explicit support for
> > it.
> > 
> > So it's going to take some detective work to find a device with ID 12.
> > 
> > Any other information on what device this might be?
> > 
> > Jonathan  
> 
> I looked through all the bosch accelerator datasheets I could find and the
> closest i could get was:
> 
> CHIP     chip_id
> BMA423 - 0x13
> BMA456 - 0x16
> 
> I'm thinking it may be the BMA422 but that datasheet isn't available for some
> reason.   I did also ask in their forums but no responses.  Unfortunately, I
> don't think it's an easy task to disassemble the screen.
> 
Without a datasheet this is hard, but you 'could' try just hacking in the
ID in the driver and see what works?  Particularly if scales match up with the
stuff on the flyer that is available for the BMA422.

Jonathan

(In reply to Jonathan Cameron from comment #5)
> On Sat, 26 Oct 2024 17:06:36 +0000
> bugzilla-daemon@kernel.org wrote:
> 
> Without a datasheet this is hard, but you 'could' try just hacking in the
> ID in the driver and see what works?  Particularly if scales match up with
> the
> stuff on the flyer that is available for the BMA422.
> 
> Jonathan

I did try hard-coding each of the 5 chip_ids from bmc150_accel_chip_info_tbl in bmc150-accel-core.c, unfortunately none of them worked.  monitor-sensor would not register any changes when moving the display panel.

I did find this which does confirm it is a BMA422 chip based on the 0x12 chip_id:

https://git.15h.org/mrothfuss/chrome-ec/src/commit/003ec08f8c67845ae8481d3fb4124555213b04c4/driver/accel_bma422.h

I'm going to mark this as resolved as we Bosch will not provide the datasheet for this chip.