On Tue, Jan 30, 2018 at 9:27 PM, Steven Presser <steve@xxxxxxxxxxxxx> wrote: > On 01/30/2018 02:05 PM, Andy Shevchenko wrote: >> On Tue, Jan 30, 2018 at 8:34 PM, Steven Presser <steve@xxxxxxxxxxxxx> >> wrote: >>> First, I believe the "bmc150" in the subject line is in some way a >>> misnomer. >>> You'd have to ask Jeremy for more details on what he intended it to refer >>> to. However, I believe the device in question is actually the bma250[1], >>> which does not have a magnetometer component. I'm unfortunately away >>> from >>> my notes, but I can check later if you need me to verify the exact chip. >> >> Please do, I would really be on the safe side here. > > Will do. My digital notes indicate I worked from what was exposed back to > what chip matched. If you can give me through Friday evening, I'll crack it > and do a visual verification. (Alas, I'm traveling and won't be back to it > until then). We are in the merge window anyway, so, no hurry. I'm looking right now in the clean solution. Looks promising. >> Bad, bad Lenovo. (DMI strings might help here) > What particular DMI strings would be helpful? All of them? Let's do this way. Create a bug on kernel bugzilla, attach output of % acpidump -o tables.dat # tables.dat file % grep -H 15 /sys/bus/acpi/devices/*/status % dmidecode and share the number here. I will take it. -- With Best Regards, Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
