From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Jeremy Cline <jeremy@jcline.org>,
linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/3] iio: accel: bmc150: Improve ACPI enumeration support
Date: Wed, 25 Nov 2020 11:49:15 +0100 [thread overview]
Message-ID: <ec8c6e1e-f914-9ee7-133f-2f55d7cc8dfb@redhat.com> (raw)
In-Reply-To: <CAHp75Vfu+PC-QzzE0_guwLHTdBXes-7RxbaS85df_p4Z=qR2=w@mail.gmail.com>
Hi,
On 11/25/20 11:41 AM, Andy Shevchenko wrote:
> On Wed, Nov 25, 2020 at 10:37 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Hi All,
>>
>> This series improves support for ACPI enumeration of bmc150 accels
>> described by an ACPI node with an ACPI hw-id of BOSC0200:
>>
>> 1. Add support for nodes which describe 2 acceleromers in a single node,
>
> accelerometers
>
>> fixing: https://bugzilla.kernel.org/show_bug.cgi?id=198671
>>
>> 2. Add support for reading the mount-matrix from the ACPI node.
>>
>> This is done in patches 2 - 3, patch 1 is a trivial cleanup which I noticed
>> could be done while working on this.
>>
>> Patch 2 is based on an earlier patch for this from Jeremy Cline:
>> https://lore.kernel.org/r/010001602cf53153-39ad69f1-1b39-4e6d-a748-9455a16c2fbd-000000@email.amazonses.com
>>
>> That patch was put on hold because normally ACPI nodes which describe
>> multiple i2c-clients in a single node are handled by:
>> drivers/platform/x86/i2c-multi-instantiate.c
>>
>> Which I tried to do at first, but as explained in the commit msg
>> of the updated patch, that is not possible in this special case
>> (because it would cause userspace breakage due to the modalias changing).
>
> This is marked as patch 1?!
Yes my bad, sorry.
> Usually --cover-letter produces a correct template...
I use --compose, time to switch to --cover-letter instead I guess.
Regards,
Hans
next prev parent reply other threads:[~2020-11-25 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 8:36 [PATCH 1/3] iio: accel: bmc150: Improve ACPI enumeration support Hans de Goede
2020-11-25 8:36 ` [PATCH 1/3] iio: accel: bmc150: Removed unused bmc150_accel_dat irq member Hans de Goede
2020-11-25 8:36 ` [PATCH 2/3] iio: accel: bmc150: Check for a second ACPI device for BOSC0200 Hans de Goede
2020-11-25 10:55 ` Andy Shevchenko
2020-11-25 11:11 ` Hans de Goede
2020-11-25 11:20 ` Andy Shevchenko
2020-11-25 16:09 ` Hans de Goede
2020-11-25 16:34 ` Andy Shevchenko
2020-11-25 8:36 ` [PATCH 3/3] iio: accel: bmc150: Get mount-matrix from ACPI Hans de Goede
2020-11-25 11:07 ` Andy Shevchenko
2020-11-25 11:12 ` Hans de Goede
2020-11-25 11:21 ` Andy Shevchenko
2020-11-25 10:41 ` [PATCH 1/3] iio: accel: bmc150: Improve ACPI enumeration support Andy Shevchenko
2020-11-25 10:49 ` Hans de Goede [this message]
2020-11-28 13:16 ` Jonathan Cameron
2020-11-28 13:32 ` Hans de Goede
2020-11-28 13:46 ` Jonathan Cameron
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=ec8c6e1e-f914-9ee7-133f-2f55d7cc8dfb@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy.shevchenko@gmail.com \
--cc=jeremy@jcline.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).