From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Peter Rosin <peda@axentia.se>, Pavel Machek <pavel@ucw.cz>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@the-dreams.de>,
Tin Huynh <tnhuynh@apm.com>, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x"
Date: Thu, 23 Mar 2017 14:16:32 +0200 [thread overview]
Message-ID: <1490271392.19767.186.camel@linux.intel.com> (raw)
In-Reply-To: <e4f3c6fd-3a91-ad9f-ba43-605f850d1524@axentia.se>
On Thu, 2017-03-23 at 12:21 +0100, Peter Rosin wrote:
> On 2017-03-23 11:04, Pavel Machek wrote:
> > On Thu 2017-03-23 08:45:58, Peter Rosin wrote:
> > > On 2017-03-22 14:05, Andy Shevchenko wrote:
> > > > On Wed, 2017-03-22 at 11:23 +0100, Peter Rosin wrote:
> > > > > On 2017-03-21 20:13, Andy Shevchenko wrote:
> Also, the general tone from Andy indicates a certain amount of
> frustration
> with the whole issue,
I'm sorry for my tone, it begins with amount of abuse case of GPIO for
ACPI in kernel followed by wilfully invented ACPI IDs in the drivers.
> which perhaps has no bearing on the seriousness,
> but what do I know?
>
> So, I'm still seeking guidance on how to handle these two patches.
I have no strong opinion, but IDs might collide in the future if PCAxxxx
will be assigned to something else and the patch will go stable@ (yeah,
OTOH it's quite unlikely).
So, we may postpone any stable@ back porting up to some real issue
appears. Regarding second one, it's not important at all (could be even
dropped). Consider it as example how to use _DSD and PRP0001 in ACPI
case for DT-enabled drivers.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-03-23 12:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:13 [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x" Andy Shevchenko
2017-03-21 19:13 ` [PATCH v1 2/2] i2c: mux: pca954x: Allow enumeration via ACPI Andy Shevchenko
2017-03-22 10:23 ` [PATCH v1 1/2] Revert "i2c: mux: pca954x: Add ACPI support for pca954x" Peter Rosin
2017-03-22 13:05 ` Andy Shevchenko
2017-03-23 7:45 ` Peter Rosin
2017-03-23 10:04 ` Pavel Machek
2017-03-23 11:21 ` Peter Rosin
2017-03-23 12:16 ` Andy Shevchenko [this message]
2017-03-24 10:21 ` Peter Rosin
2017-03-26 12:47 ` Andy Shevchenko
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=1490271392.19767.186.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=peda@axentia.se \
--cc=rpurdie@rpsys.net \
--cc=tnhuynh@apm.com \
--cc=wsa@the-dreams.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.