All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-iio@vger.kernel.org, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-acpi@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 1/5] iio: proximity: sx9500: Assign interrupt from GpioIo()
Date: Sun, 19 Nov 2017 15:24:11 +0000	[thread overview]
Message-ID: <20171119152411.12e4c7cb@archlinux> (raw)
In-Reply-To: <20171106093556.GR2283@lahna.fi.intel.com>

On Mon, 6 Nov 2017 11:35:56 +0200
Mika Westerberg <mika.westerberg@linux.intel.com> wrote:

> On Sat, Nov 04, 2017 at 03:11:19AM +0000, Jonathan Cameron wrote:
> > On Fri, 3 Nov 2017 15:03:36 +0200
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> >   
> > > The commit 0f0796509c07
> > > 
> > > ("iio: remove gpio interrupt probing from drivers that use a single
> > > interrupt")
> > > 
> > > removed custom IRQ assignment for the drivers which are enumerated via
> > > ACPI or OF. Unfortunately, some ACPI tables have IRQ line defined as
> > > GpioIo() resource and thus automatic IRQ allocation will fail.  
> > 
> > I'll ask the obvious question - is this allowed under the ACPI spec?  
> 
> Yes, it is perfectly fine.

I'm unconvinced...

> 
> > > Partially revert the commit 0f0796509c07 to restore original
> > > behaviour.
> > > 
> > > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>  
> > 
> > I really don't like scattering fixes for broken ACPI tables through
> > drivers...  Is there really no better solution to this?  
> 
> This is not about broken ACPI tables. We just currently have
> "convenience" stuff in the kernel that translates trivial things like a
> single ACPI GpioInt() resource directly to a device interrupt. If the
> table has multiple GpioInt()s or uses GpioIo() then it is up to the
> driver to handle device specific details.

I agree on the multiple cases needing hanlding. 
What bothers me is that there is no guarantee at all that a GpioIo
can even do an interrupt.

(table 6.2.17 in the 6.1 spec for example makes it clear that we are
in a mess)  If it is a gpioio lots of the interrupt specific stuff
cannot be supplied (all the stuff in byte 7)

So as I read the ACPI specification any interrupt specified as GpioIO
is simply broken.

> 
> > On patches like this best to pull in ACPI and GPIO on the cc list.
> > 
> > Also cc'd Mika who made the original change to support gpioint.  
> 
> The patch looks fine to me,
> 
> Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

I'll probably take it anyway to support the platforms doing this particular
piece of fun as doubtlessly the chance of fixing the firmware is next
to nothing...

Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2017-11-19 15:24 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 13:03 [PATCH v3 1/5] iio: proximity: sx9500: Assign interrupt from GpioIo() Andy Shevchenko
2017-11-03 13:03 ` [PATCH v3 2/5] iio: proximity: sx9500: Add GPIO ACPI mapping table Andy Shevchenko
     [not found]   ` <20171103130340.42459-2-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-11-04  3:14     ` Jonathan Cameron
2017-11-04  3:14       ` Jonathan Cameron
2017-11-19 15:29       ` Jonathan Cameron
2017-11-19 15:29         ` Jonathan Cameron
2017-11-25 14:24         ` Jonathan Cameron
2017-11-25 14:24           ` Jonathan Cameron
2017-11-27 15:08           ` Andy Shevchenko
     [not found]             ` <1511795292.25007.454.camel-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-12-01 10:04               ` Linus Walleij
2017-12-01 10:04                 ` Linus Walleij
2017-12-01 12:36                 ` Andy Shevchenko
2017-11-03 13:03 ` [PATCH v3 3/5] iio: proximity: sx9500: Set IRQ pin to direction-input if necessary Andy Shevchenko
2017-11-04  3:20   ` Jonathan Cameron
2017-11-08 16:35     ` Andy Shevchenko
2017-11-08 17:03       ` Mika Westerberg
2017-11-08 20:45         ` Linus Walleij
2017-11-08 20:52           ` Andy Shevchenko
2017-11-10 18:13           ` Andy Shevchenko
2018-02-26 19:51         ` Andy Shevchenko
2017-11-03 13:03 ` [PATCH v3 4/5] iio: proximity: sx9500: Add another ACPI ID Andy Shevchenko
2017-11-19 15:32   ` Jonathan Cameron
2017-11-03 13:03 ` [PATCH v3 5/5] iio: magnetometer: ak8975: " Andy Shevchenko
2017-11-04  3:11 ` [PATCH v3 1/5] iio: proximity: sx9500: Assign interrupt from GpioIo() Jonathan Cameron
2017-11-04  3:11   ` Jonathan Cameron
2017-11-04 10:43   ` Linus Walleij
     [not found]   ` <20171104031119.00006e56-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-06  9:35     ` Mika Westerberg
2017-11-06  9:35       ` Mika Westerberg
2017-11-19 15:24       ` Jonathan Cameron [this message]
2017-11-20 10:30         ` Mika Westerberg
2017-11-25 14:28           ` 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=20171119152411.12e4c7cb@archlinux \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --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 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.