[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE=gft6qb9aBJTrTL_QE=LATh+1+J1gaWjtXs_OXhEbCdgm0jw@mail.gmail.com>
Date: Sun, 17 Jan 2021 09:15:06 -0800
From: Evan Green <evgreen@...omium.org>
To: Wolfram Sang <wsa@...nel.org>
Cc: Peter Rosin <peda@...ntia.se>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Randy Dunlap <rdunlap@...radead.org>,
Peter Korsgaard <peter.korsgaard@...co.com>,
linux-i2c <linux-i2c@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in
ACPI land
On Sun, Jan 17, 2021 at 3:54 AM Wolfram Sang <wsa@...nel.org> wrote:
>
> On Wed, Nov 18, 2020 at 03:40:25PM -0800, Evan Green wrote:
> > Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> > property translates directly to a fwnode_property_*() call. The child
> > reg property translates naturally into _ADR in ACPI.
> >
> > The i2c-parent binding is a relic from the days when the bindings
> > dictated that all direct children of an I2C controller had to be I2C
> > devices. These days that's no longer required. The i2c-mux can sit as a
> > direct child of its parent controller, which is where it makes the most
> > sense from a hardware description perspective. For the ACPI
> > implementation we'll assume that's always how the i2c-mux-gpio is
> > instantiated.
> >
> > Signed-off-by: Evan Green <evgreen@...omium.org>
>
> Applied to for-next, thanks! The code Andy mentioned can still be
> refactored later if new ACPI helpers appear in the future.
Thanks Wolfram and Peter!
Powered by blists - more mailing lists