Received: by 10.223.176.5 with SMTP id f5csp1054871wra; Tue, 6 Feb 2018 11:48:33 -0800 (PST) X-Google-Smtp-Source: AH8x224DNvUuipS4qDJHGrqZoG1d+E/QDuTghC2FJj99tUvr3k6BJ22qA34G3JXcO4tKUdOO9ZM4 X-Received: by 2002:a17:902:5a3:: with SMTP id f32-v6mr3505967plf.48.1517946513379; Tue, 06 Feb 2018 11:48:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517946513; cv=none; d=google.com; s=arc-20160816; b=Zk6KpI5RM8jrmzXOfkVS9bf5UaCA836bmSIba7nBlbUyWmO1cPCqhID2PoEdYH3Q56 4rZ4TVXOAm+nEmFVv8XIrN9imnUNM37XVdxmYPWECbsUsw8Wt17/jJgWRFUSMCNq3M3+ LFxJVmnSXbsPN//jDguL8M+/8/t8zINfN5w789BkPlRGGGlJRSFOrGNgjFXEbzrEM0f4 dNBM5Glv0PzKXGeO9RhQewWQ01EDqM6NxlgUNn9KES0yHr6dY8grEuRZJh1a/jMYs4kN Dc3/bKNidArIMPFnlCJ/UnUjOteVu7qUHNUPPgogwDyoZIjdGLe2fxeEYP0pIVcyiL27 8WCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=ROuPQmxLpp5tEC7CVc+WHb/0TXRl2TWe7f/JmW1p1Hg=; b=qb9FtTX6cLfIrunwZHikUnSxFoLF7IdpvfCBsPLgOzpJnjLuyPE/4y7mhN0m0z2zWw Z0FGgLDhSNNcxKw0kTixZX1BTkSIsLu8l9jRRWJI6cY27JAxnhLq1a+uhY+gr4KPhfQh 3+D2UG0qMS3tPrBDXUuO4Pw1e1vYmNqoVKNN4Fd/KQWFegF0Vt2GMn8Qs7sD5IoNwZfG ulqqg5adpEtjtyI4hEPl8J28X0iIzjs0a02B0kzNXL/01wikeuVZ8d1bjkxfbpF1A73C ZigD4ebbMsY7SpUaSePV9UTHbifLyqifiZi9AruxoZehN1c7hKzW84z6VCHu/WHK6pT2 wq0w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=aDEd0BAJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y7-v6si1528795plh.806.2018.02.06.11.48.19; Tue, 06 Feb 2018 11:48:33 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=aDEd0BAJ; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753394AbeBFTrc (ORCPT + 99 others); Tue, 6 Feb 2018 14:47:32 -0500 Received: from mail-qt0-f169.google.com ([209.85.216.169]:45650 "EHLO mail-qt0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752873AbeBFTra (ORCPT ); Tue, 6 Feb 2018 14:47:30 -0500 Received: by mail-qt0-f169.google.com with SMTP id x27so3867807qtm.12; Tue, 06 Feb 2018 11:47:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ROuPQmxLpp5tEC7CVc+WHb/0TXRl2TWe7f/JmW1p1Hg=; b=aDEd0BAJj9vJoOO4xoOXXQOh+DGD03e16T5z/F0vYsLiLxsRsuOpVNBtzr/UY+HYK2 W27nSc50DV1FE/gE/v6r1c4ZShJMvKWnB85z1WTXLTbHxmziRZy+H0bouvj5XDB1eYiM xzGs/vT0ah8Sd7+gKr0BADgm83g3apti2LgNaJeLLCU/IHTcMg+7mDAlLP1/JqU6Pba7 NI4Sc65fvtjNXSeJhKi04voMurv1SKm+8Sq6E3C5HvHusuBqTKW49rFDCdzygYmyysce B3IpC3WPxKefBKymAJBuEQDCQH6UWhslsXITPEdezHLKLUy99zWV4WOetuAOpbZk7Cdk PKig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ROuPQmxLpp5tEC7CVc+WHb/0TXRl2TWe7f/JmW1p1Hg=; b=BS6Q/fDg68A7M52xHTLZRHoSEQUSx6nEQTEwle8rRuWCUIkoIGnUSDtGUskX89OToH QrVVBjXzCQPQVzX222M6LlVCM1ZVaIVw4dfyftsZvZ0BuiEF7wwyY+h1vBy7tlDmV5ek 2EeOAPW75vF4HfyTMlZDvRGl2tF5Mv9/Y9JLfUTkAp2DGTILdiwMHrf02xcDo/NTapz9 BHASCyKGe0WPYtrGJ4i7iGKCuqv3/4JV6WLOjtQFuJgZG7nM+BEgVUf8eNcl4iWlsgl1 w2sjal1152Bd9Ml2bICI9Z32ukljrermeX2vc0r/TFvarKZphdj3SsW90ycOyG6M1RiU e4rQ== X-Gm-Message-State: APf1xPDeZbEMFyVcrB337Vux57n5ZavaH8SR1NDy7NmXNSraVhryLPH9 miac1SYtsvwMAEPs9CFxhHUKbZaIs8qjD1+Qorw= X-Received: by 10.200.3.104 with SMTP id w40mr5192789qtg.149.1517946449480; Tue, 06 Feb 2018 11:47:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.175.35 with HTTP; Tue, 6 Feb 2018 11:47:28 -0800 (PST) In-Reply-To: <9ee7da52-d86a-7784-8c00-6e5b4ae3ed96@pressers.name> References: <010001602cf53153-39ad69f1-1b39-4e6d-a748-9455a16c2fbd-000000@email.amazonses.com> <20171210182152.70ad8fbf@archlinux> <01000160dccefcb4-25edfd89-56f3-486f-88a4-cb8c07253974-000000@email.amazonses.com> <20180114104330.2aa7c1fd@archlinux> <20180128094021.572ab366@archlinux> <20180130160107.000006df@huawei.com> <197f448e-322f-dae4-aa4b-3cc2bd5b16bb@pressers.name> <9ee7da52-d86a-7784-8c00-6e5b4ae3ed96@pressers.name> From: Andy Shevchenko Date: Tue, 6 Feb 2018 21:47:28 +0200 Message-ID: Subject: Re: [PATCH v2] iio: accel: bmc150: Check for a second ACPI device for BOSC0200 To: Steven Presser Cc: Hans de Goede , Hartmut Knaack , Jeremy Cline , Jonathan Cameron , Jonathan Cameron , Lars Kellogg-Stedman , Lars-Peter Clausen , Linux Kernel Mailing List , Mika Westerberg , Peter Meerwald-Stadler , Wolfram Sang , linux-iio@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Feb 4, 2018 at 7:58 PM, Steven Presser wrote: > I had a chance to sit back down with the machine. I didn't take it all the > way apart - there are pieces that I'm afraid of breaking without directions > on how to properly disassemble them. No need I think to go so-o deep. > However, I did recover an exact chip ID - the chips in use are BMA255s [1]. > Rather than take the machine apart (and because the chips are 2mmx2mm), I > queried the chip over SMBus. On page 50 of the below document, you can see > that register 0x00 is a read-only chip ID. This chipID is unique per Bosch > product. So, using SMBus, I asked the chip for it's chip ID (0xFA, in this > case) and then searched likely products until I found the matching chipID. Thanks! > Does this suffice to settle which chips are in use? If not, I can finish > taking the machine apart, I'd just prefer to avoid the risk of breaking > something. I think it's pretty much enough. > As soon as I finish screwing everything back together, I'll grab the other > software IDs asked for and build the branch referenced elsewhere. I'm just waiting for your Tested-by in case my patch series works as expected before I send it out. -- With Best Regards, Andy Shevchenko