Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1464401
| From | Mika Westerberg <mika.westerberg@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe |
| Date | 2016-08-17 10:20 +0200 |
| Message-ID | <s74eR-6Pr-23@gated-at.bofh.it> (permalink) |
| References | <psQ26-856-11@gated-at.bofh.it> <pwucH-5HT-9@gated-at.bofh.it> <pwUTw-30i-13@gated-at.bofh.it> <pwVcS-3CW-5@gated-at.bofh.it> <s6PfP-5j1-25@gated-at.bofh.it> |
| Organization | Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo |
On Tue, Aug 16, 2016 at 06:12:40PM +0200, Anisse Astier wrote: > Hi Mika, > > On Tue, Jun 2, 2015 at 4:15 PM, Mika Westerberg > <mika.westerberg@linux.intel.com> wrote: > > On Tue, Jun 02, 2015 at 03:53:40PM +0200, Linus Walleij wrote: > >> On Mon, Jun 1, 2015 at 11:23 AM, Mika Westerberg > >> <mika.westerberg@linux.intel.com> wrote: > >> > On Fri, May 22, 2015 at 10:56:08AM +0300, Mika Westerberg wrote: > >> >> BIOS/platform may use some of the pins by themselves, such as providing SCI > >> >> (System Control Interrupt) from the embedded controller. The driver masks > >> >> all interrupts at probe time which prevents those pins from triggering > >> >> interrupts properly. > >> >> > >> >> Fix this by not masking all interrupts at probe -- it should be enough just > >> >> to clear the status register. > >> >> > >> >> Reported-by: Yu C Chen <yu.c.chen@intel.com> > >> >> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> > >> > > >> > Please ignore this patch for now. It turned out to be causing spurious > >> > interrupts on another platform. > >> > > >> > I'll need to rethink how to fix the reported issue. > >> > >> Looks like a case of "embed more magic knowledge" in the driver :/ > >> > >> It needs to know what platform it is running on, and only leave specific > >> bits unmasked on these specific platforms. Right? Thereby > >> tossing all of the acpi_device_id matching and abstraction out > >> of the window. > > > > That's right. > > > > We still have few options left, like using ACPI _AEI (ACPI GPIO > > triggered events) for this or adding GPIO interrupt support directly to > > the EC driver. > > Did you find a way to fix this issue ? I'm seeing a similar problem on a > laptop where this masks the interrupt used for ACPI events (brightness, > lid, battery). I seem to have forgotten this completely :-/ Can you send me output of /sys/kernel/debug/pinctrl/INT33FF:*/pins for that particular EC pin? In addition if you apply this patch do you see that ACPI events start working?
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Anisse Astier <anisse@astier.eu> - 2016-08-16 18:20 +0200
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-08-17 10:20 +0200
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Anisse Astier <anisse@astier.eu> - 2016-08-17 15:50 +0200
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-08-18 14:20 +0200
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Anisse Astier <anisse@astier.eu> - 2016-08-18 16:00 +0200
Re: [PATCH] pinctrl: cherryview: Do not mask all interrupts on probe Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-08-18 16:00 +0200
csiph-web