[Bug 219418] BOSC0200 Accelerometer Invalid chip 12 initialization error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=219418

--- Comment #5 from Jonathan Cameron (jic23@xxxxxxxxxx) ---
On Sat, 26 Oct 2024 17:06:36 +0000
bugzilla-daemon@xxxxxxxxxx wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=219418
> 
> --- Comment #4 from Camera Phone (cameraphone77@xxxxxxxxx) ---
> (In reply to Jonathan Cameron from comment #3)
> > On Tue, 22 Oct 2024 13:17:20 +0000
> > bugzilla-daemon@xxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxx
> > >           Reporter: cameraphone77@xxxxxxxxx
> > >         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

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Input]     [Linux Kernel]     [Linux SCSI]     [X.org]

  Powered by Linux