All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-iio@vger.kernel.org
Subject: [Bug 219418] BOSC0200 Accelerometer Invalid chip 12 initialization error
Date: Sun, 27 Oct 2024 19:43:25 +0000	[thread overview]
Message-ID: <bug-219418-217253-tGfKE3wATs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219418-217253@https.bugzilla.kernel.org/>

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

--- Comment #6 from Camera Phone (cameraphone77@gmail.com) ---
(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

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

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

  parent reply	other threads:[~2024-10-27 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-22 13:17 [Bug 219418] New: BOSC0200 Accelerometer Invalid chip 12 initialization error bugzilla-daemon
2024-10-22 13:17 ` [Bug 219418] " bugzilla-daemon
2024-10-22 13:17 ` bugzilla-daemon
2024-10-26 14:49 ` [Bug 219418] New: " Jonathan Cameron
2024-10-26 14:49 ` [Bug 219418] " bugzilla-daemon
2024-10-26 17:06 ` bugzilla-daemon
2024-10-27 10:34   ` Jonathan Cameron
2024-10-27 10:34 ` bugzilla-daemon
2024-10-27 19:43 ` bugzilla-daemon [this message]
2024-12-12  1:48 ` bugzilla-daemon

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=bug-219418-217253-tGfKE3wATs@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-iio@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.