Skip to contentSkip to conversation

bmc150_accel i2c-BMA250E:00: Invalid chip f8

DISCUSSION Bastien Nocera 3 participants 6 messages Jul 22, 2015 – Jul 23, 2015 IIO

lore
Share & tools
lore

Bastien Nocera

author
#0 lore raw

Hey,

Running kernel 4.0.8 on a WinBook TW100 tablet, I get the error message in the subject line when loading the bmc150_accel driver.

The 2 items in udev about that device:
P: /devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=acpi

and:
P: /devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: DEVPATH=/devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=i2c

And the DSDT for the device:
https://people.gnome.org/~hadess/Winbook%20TW100%20DSDT.dsl

Any ideas what I should try (apart from a more recent kernel, I'm onto that...)

Cheers

#1 lore raw

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogbGludXgtaWlvLW93bmVy QHZnZXIua2VybmVsLm9yZyBbbWFpbHRvOmxpbnV4LWlpby1vd25lckB2Z2VyLmtlcm5lbC5vcmdd IE9uIEJlaGFsZiBPZiBCYXN0aWVuIE5vY2VyYQ0KPiBTZW50OiAyMiBKdWx5LCAyMDE1IDIxOjQ5 DQo+IFRvOiBsaW51eC1paW9Admdlci5rZXJuZWwub3JnDQo+IFN1YmplY3Q6IGJtYzE1MF9hY2Nl bCBpMmMtQk1BMjUwRTowMDogSW52YWxpZCBjaGlwIGY4DQo+IA0KPiBIZXksDQo+IA0KPiBSdW5u aW5nIGtlcm5lbCA0LjAuOCBvbiBhIFdpbkJvb2sgVFcxMDAgdGFibGV0LCBJIGdldCB0aGUgZXJy b3IgbWVzc2FnZQ0KPiBpbiB0aGUgc3ViamVjdCBsaW5lIHdoZW4gbG9hZGluZyB0aGUgYm1jMTUw X2FjY2VsIGRyaXZlci4NCj4gDQo+IFRoZSAyIGl0ZW1zIGluIHVkZXYgYWJvdXQgdGhhdCBkZXZp Y2U6DQo+IFA6IC9kZXZpY2VzL0xOWFNZU1RNOjAwL0xOWFNZQlVTOjAwLzgwODYwRjQxOjA0L0JN QTI1MEU6MDANCj4gRTogREVWUEFUSD0vZGV2aWNlcy9MTlhTWVNUTTowMC9MTlhTWUJVUzowMC84 MDg2MEY0MTowNC9CTUEyNTBFOjAwDQo+IEU6IE1PREFMSUFTPWFjcGk6Qk1BMjUwRTpCTUEyNTBF Og0KPiBFOiBTVUJTWVNURU09YWNwaQ0KPiANCj4gYW5kOg0KPiBQOiAvZGV2aWNlcy9wbGF0Zm9y bS84MDg2MEY0MTowNC9pMmMtMTIvaTJjLUJNQTI1MEU6MDANCj4gRTogREVWUEFUSD0vZGV2aWNl cy9wbGF0Zm9ybS84MDg2MEY0MTowNC9pMmMtMTIvaTJjLUJNQTI1MEU6MDANCj4gRTogTU9EQUxJ QVM9YWNwaTpCTUEyNTBFOkJNQTI1MEU6DQo+IEU6IFNVQlNZU1RFTT1pMmMNCj4gDQo+IEFuZCB0 aGUgRFNEVCBmb3IgdGhlIGRldmljZToNCj4gaHR0cHM6Ly9wZW9wbGUuZ25vbWUub3JnL35oYWRl c3MvV2luYm9vayUyMFRXMTAwJTIwRFNEVC5kc2wNCj4gDQo+IEFueSBpZGVhcyB3aGF0IEkgc2hv dWxkIHRyeSAoYXBhcnQgZnJvbSBhIG1vcmUgcmVjZW50IGtlcm5lbCwgSSdtIG9udG8NCj4gdGhh dC4uLikNCg0KSGkgQmFzdGllbiwNCg0KU2VlbXMgdG8gbWUgdGhhdCB0aGUgQUNQSSB0YWJsZSBk ZWNsYXJlcyB5b3UgaGF2ZSBCTUEyNTBFIGNoaXAsIGJ1dA0KdGhlIGhhcmR3YXJlIGlzIGFjdHVh bGx5IEJNQTIyMkUuIEJvc2ggYWNjZWxlcm9tZXRlciBCTUEyNTBFIGhhcyBjaGlwDQpJRCAweEY5 IFsxXSwgd2hpbGUgQk1BMjIyRSBoYXMgY2hpcCBJRCAweEY4IFsyXS4NClRoZXNlIGNoaXBzIGFy ZSB2ZXJ5IHNpbWlsYXIsIGV4Y2VwdCBmb3IgdGhlIGNoaXAgaWQgYW5kIHgveS96IHJlc29sdXRp b24uDQoNCllvdSBjb3VsZCB0cnkgZm9yY2luZyB0aGUgZHJpdmVyIHRvIHVzZSBibWEyMjJlIGZv ciB5b3VyIEFDUEkgSUQgYW5kIHNlZQ0KaWYgdGhlIHZhbHVlcyB5b3UgZ2V0IGZvciBhY2NlbGVy YXRpb24gYXJlIE9LLiBZb3UgbmVlZCB0byBkbyBzb21ldGhpbmcNCmxpa2UgdGhpczoNCg0KZGlm ZiAtLWdpdCBhL2RyaXZlcnMvaWlvL2FjY2VsL2JtYzE1MC1hY2NlbC5jIGIvZHJpdmVycy9paW8v YWNjZWwvYm1jMTUwLWFjY2VsLmMNCmluZGV4IDQ3YzYwMTMuLjVjYjQxM2EgMTAwNjQ0DQotLS0g YS9kcml2ZXJzL2lpby9hY2NlbC9ibWMxNTAtYWNjZWwuYw0KKysrIGIvZHJpdmVycy9paW8vYWNj ZWwvYm1jMTUwLWFjY2VsLmMNCkBAIC0xODM5LDcgKzE4MzksNyBAQCBzdGF0aWMgY29uc3Qgc3Ry dWN0IGFjcGlfZGV2aWNlX2lkIGJtYzE1MF9hY2NlbF9hY3BpX21hdGNoW10gPSB7DQogICAgICAg IHsiQk1DMTUwQSIsICAgICBibWMxNTB9LA0KICAgICAgICB7IkJNSTA1NUEiLCAgICAgYm1pMDU1 fSwNCiAgICAgICAgeyJCTUEwMjU1IiwgICAgIGJtYTI1NX0sDQotICAgICAgIHsiQk1BMjUwRSIs ICAgICBibWEyNTBlfSwNCisgICAgICAgeyJCTUEyNTBFIiwgICAgIGJtYTIyMmV9LA0KICAgICAg ICB7IkJNQTIyMkUiLCAgICAgYm1hMjIyZX0sDQogICAgICAgIHsiQk1BMDI4MCIsICAgICBibWEy ODB9LA0KICAgICAgICB7IH0sDQoNCkluIGNhc2UgaXQgd29ya3MgeW91IHByb2JhYmx5IG5lZWQg dG8gbW9kaWZ5IHlvdXIgQUNQSSB0YWJsZS4NCg0KVGhhbmtzLA0KSXJpbmENCg0KWzFdIGh0dHBz Oi8vYWUtYnN0LnJlc291cmNlLmJvc2NoLmNvbS9tZWRpYS9wcm9kdWN0cy9kb2t1bWVudGUvYm1h MjUwZS9CU1QtQk1BMjUwRS1EUzAwNC0wNV9wdWJsaXNoZWQucGRmDQpbMl0gaHR0cHM6Ly9hZS1i c3QucmVzb3VyY2UuYm9zY2guY29tL21lZGlhL3Byb2R1Y3RzL2Rva3VtZW50ZS9ibWEyMjJlL0JT VC1CTUEyMjJFLURTMDA0LTA1X3B1Ymxpc2hlZC5wZGYNCg0KDQo+IA0KPiBDaGVlcnMNCj4gLS0N Cj4gVG8gdW5zdWJzY3JpYmUgZnJvbSB0aGlzIGxpc3Q6IHNlbmQgdGhlIGxpbmUgInVuc3Vic2Ny aWJlIGxpbnV4LWlpbyIgaW4NCj4gdGhlIGJvZHkgb2YgYSBtZXNzYWdlIHRvIG1ham9yZG9tb0B2 Z2VyLmtlcm5lbC5vcmcNCj4gTW9yZSBtYWpvcmRvbW8gaW5mbyBhdCAgaHR0cDovL3ZnZXIua2Vy bmVsLm9yZy9tYWpvcmRvbW8taW5mby5odG1sDQo=

author
#2 lore raw
Quoted 33 lines · Irina
Quoted 26 lines

-----Original Message-----
From: [email protected] [mailto:
[email protected]] On Behalf Of Bastien Nocera
Sent: 22 July, 2015 21:49
To: [email protected]
Subject: bmc150_accel i2c-BMA250E:00: Invalid chip f8

Hey,

Running kernel 4.0.8 on a WinBook TW100 tablet, I get the error message
in the subject line when loading the bmc150_accel driver.

The 2 items in udev about that device:
P: /devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=acpi

and:
P: /devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: DEVPATH=/devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=i2c

Quoted 6 lines

And the DSDT for the device:
https://people.gnome.org/~hadess/Winbook%20TW100%20DSDT.dsl

Any ideas what I should try (apart from a more recent kernel, I'm onto
that...)

Quoted 5 lines

Hi Bastien,

Seems to me that the ACPI table declares you have BMA250E chip, but the hardware is actually BMA222E. Bosh accelerometer BMA250E has chip ID 0xF9 [1], while BMA222E has chip ID 0xF8 [2].

I gathered as much from reading the driver.

Quoted 6 lines

These chips are very similar, except for the chip id and x/y/z resolution.

You could try forcing the driver to use bma222e for your ACPI ID and see
if the values you get for acceleration are OK.

Will try that.
<snip>

Quoted 1 line

In case it works you probably need to modify your ACPI table.

But I won't do that. Windows works on the same system, and so should Linux. I'm guessing that the Linux driver is more stringent than the Windows one.

I'd do something like:
- ACPI ID just tells you which driver to load, not which variant it actually is.
- Use the chip ID to see which variant of the chipset it is

I'll test that after identifying which of the variants it is.

Cheers

#3 lore raw
In reply to Bastien Nocera
Quoted 17 lines · Bastien Nocera

Hey,

Running kernel 4.0.8 on a WinBook TW100 tablet, I get the error message in the subject line when loading the bmc150_accel driver.

The 2 items in udev about that device:
P: /devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=acpi

and:
P: /devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: DEVPATH=/devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=i2c

Quoted 5 lines

And the DSDT for the device:
https://people.gnome.org/~hadess/Winbook%20TW100%20DSDT.dsl

Any ideas what I should try (apart from a more recent kernel, I'm onto that...)

Odd. The bma250e is documented as having an id of 0xf9 not 0xf8.
http://ae-bst.resource.bosch.com/media/products/dokumente/bma250e/BST-BMA250 E-DS004-05_published.pdf

So all I can think of is that the chip is a bma222e (or something else with the 0xf8 chip id) or there are some bma250e's out there with the wrong ID...

Someone changed a part on the device and thought no one would notice and hence didn't update the bios? (even if it has a totally different range)

I guess if you frig the driver to load anyway we can see what value it is giving for g and that should give us more of a clue.

Jonathan

Quoted 6 lines

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#4 lore raw
Quoted 32 lines · [email protected] writes:
Quoted 17 lines · Bastien Nocera

Hey,

Running kernel 4.0.8 on a WinBook TW100 tablet, I get the error message in the subject line when loading the bmc150_accel driver.

The 2 items in udev about that device:
P: /devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/80860F41:04/BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=acpi

and:
P: /devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: DEVPATH=/devices/platform/80860F41:04/i2c-12/i2c-BMA250E:00
E: MODALIAS=acpi:BMA250E:BMA250E:
E: SUBSYSTEM=i2c

Quoted 5 lines

And the DSDT for the device:
https://people.gnome.org/~hadess/Winbook%20TW100%20DSDT.dsl

Any ideas what I should try (apart from a more recent kernel, I'm onto that...)

Odd. The bma250e is documented as having an id of 0xf9 not 0xf8.
http://ae-bst.resource.bosch.com/media/products/dokumente/bma250e/BST-BMA2 50 E-DS004-05_published.pdf

So all I can think of is that the chip is a bma222e (or something else with the 0xf8 chip id) or there are some bma250e's out there with the wrong ID...

Quoted 9 lines

Someone changed a part on the device and thought no one would notice and hence didn't update the bios? (even if it has a totally different range)

I guess if you frig the driver to load anyway we can see what value it is giving for g and that should give us more of a clue.

Jonathan

Sorry, on webmail today and missed the existing follow ups!

Quoted 11 lines
Quoted 7 lines

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

author
#5 lore raw
In reply to [email protected]
Quoted 1 line · On Thu, 2015-07-23 at 14:59 +0100, [email protected] wrote:

<snip>

Quoted 10 lines

Odd. The bma250e is documented as having an id of 0xf9 not 0xf8.
http://ae-bst.resource.bosch.com/media/products/dokumente/bma250e/BST
-BMA250
E-DS004-05_published.pdf

So all I can think of is that the chip is a bma222e (or something else
with the 0xf8 chip id) or there are some bma250e's out there with the wrong ID...

Quoted 6 lines

Someone changed a part on the device and thought no one would notice and hence didn't update the bios? (even if it has a totally different range)

I guess if you frig the driver to load anyway we can see what value it is giving for g and that should give us more of a clue.

I've sent 1 preparation patch, and one fixup patch to ignore the ACPI/I2C ID when selecting the chip type.

Cheers