From: Mateusz K <mateusz.kaduk@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, Lee Jones <lee@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] mfd: intel-lpss: Switch over to MSI interrupts
Date: Tue, 26 Mar 2024 15:50:37 +0100 [thread overview]
Message-ID: <CAPf=4Rdc6pHy34dSKex_KOmeAo2bsuaGv5X6MyJ6+Se5h3Mo4w@mail.gmail.com> (raw)
In-Reply-To: <ZgLefFQanbq-ozKM@smile.fi.intel.com>
Maybe it's much to ask, but I would really appreciate it if someone
looked into intel-lpss supporting these devices.
Been using a laptop without a functional touchpad over months now.
If that helps, there is another thread here
https://bugzilla.kernel.org/show_bug.cgi?id=218444 with perhaps more
details on the problem.
Battery and speaker are not a big deal, but the not working touchpad,
which I believe should be handled by an intel-lpss driver, is kind of
painful.
If you need any help from my side, testing patches, don't hesitate to
contact me.
Regards,
Mateusz
On Tue, Mar 26, 2024 at 3:41 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> On Tue, Mar 26, 2024 at 11:06:38AM +0100, Mateusz K wrote:
> > I tried the patch that changes PCI_IRQ_LEGACY into PCI_IRQ_ALL_TYPES
> > and it seems I get some other error now
> >
> > [ 1.477341] intel-lpss 0000:00:15.0: enabling device (0004 -> 0006)
> > [ 1.477466] intel-lpss 0000:00:15.0: can't derive routing for PCI INT A
> > [ 1.477468] intel-lpss 0000:00:15.0: PCI INT A: not connected
> > [ 1.477488] intel-lpss 0000:00:15.0: probe with driver intel-lpss
> > failed with error -2147483648
> > [ 1.489572] intel-lpss 0000:00:15.2: enabling device (0004 -> 0006)
> > [ 1.489688] intel-lpss 0000:00:15.2: can't derive routing for PCI INT C
> > [ 1.489689] intel-lpss 0000:00:15.2: PCI INT C: not connected
> > [ 1.489715] intel-lpss 0000:00:15.2: probe with driver intel-lpss
> > failed with error -2147483648
> > [ 1.501886] intel-lpss 0000:00:19.0: enabling device (0004 -> 0006)
> > [ 1.502034] intel-lpss 0000:00:19.0: can't derive routing for PCI INT A
> > [ 1.502036] intel-lpss 0000:00:19.0: PCI INT A: not connected
> > [ 1.502067] intel-lpss 0000:00:19.0: probe with driver intel-lpss
> > failed with error -2147483648
> > [ 1.514288] intel-lpss 0000:00:19.1: enabling device (0004 -> 0006)
> > [ 1.514535] intel-lpss 0000:00:19.1: can't derive routing for PCI INT B
> > [ 1.514538] intel-lpss 0000:00:19.1: PCI INT B: not connected
> > [ 1.514570] intel-lpss 0000:00:19.1: probe with driver intel-lpss
> > failed with error -2147483648
> > [ 1.526291] intel-lpss 0000:00:1e.0: enabling device (0004 -> 0006)
> > [ 1.526555] intel-lpss 0000:00:1e.0: can't derive routing for PCI INT A
> > [ 1.526557] intel-lpss 0000:00:1e.0: PCI INT A: not connected
> > [ 1.526604] intel-lpss 0000:00:1e.0: probe with driver intel-lpss
> > failed with error -2147483648
> > [ 1.538130] intel-lpss 0000:00:1e.3: enabling device (0004 -> 0006)
> > [ 1.538233] intel-lpss 0000:00:1e.3: can't derive routing for PCI INT D
> > [ 1.538235] intel-lpss 0000:00:1e.3: PCI INT D: not connected
> > [ 1.538253] intel-lpss 0000:00:1e.3: probe with driver intel-lpss
> > failed with error -2147483648
>
> Hmm... I have a unique board to test :-)
> Let's revert it then.
>
> Bjorn, in such case your tree should keep conversion one.
>
> Lee, do you prefer a revert or can you simply drop this from the queue?
>
> --
> With Best Regards,
> Andy Shevchenko
>
>
next prev parent reply other threads:[~2024-03-26 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:59 [PATCH v1 1/1] mfd: intel-lpss: Switch over to MSI interrupts Andy Shevchenko
2024-03-21 16:02 ` (subset) " Lee Jones
2024-03-25 21:19 ` Bjorn Helgaas
2024-03-26 10:06 ` Mateusz K
2024-03-26 14:41 ` Andy Shevchenko
2024-03-26 14:50 ` Mateusz K [this message]
2024-03-26 15:25 ` Andy Shevchenko
2024-03-26 15:24 ` Andy Shevchenko
2024-03-27 13:17 ` Lee Jones
2024-03-27 13:24 ` Andy Shevchenko
2024-03-27 14:12 ` Lee Jones
2024-03-27 14:23 ` Andy Shevchenko
2024-03-26 16:21 ` Andy Shevchenko
2024-03-26 21:01 ` Bjorn Helgaas
2024-03-26 21:22 ` Andy Shevchenko
2024-03-26 22:09 ` Bjorn Helgaas
2024-03-26 22:25 ` 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='CAPf=4Rdc6pHy34dSKex_KOmeAo2bsuaGv5X6MyJ6+Se5h3Mo4w@mail.gmail.com' \
--to=mateusz.kaduk@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.