From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Darren Stevens <darren@stevens-zone.net>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
mad skateman <madskateman@gmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [FSL P50x0] Keyboard and mouse don't work anymore after the devicetree updates for 5.19
Date: Fri, 27 May 2022 07:23:05 +0000 [thread overview]
Message-ID: <2e1b72bd-ae44-19d1-5981-09f5c69759dc@csgroup.eu> (raw)
In-Reply-To: <283c811b-27f7-64a8-8a67-11cf6c3a79cf@xenosoft.de>
Hi
Le 26/05/2022 à 19:42, Christian Zigotzky a écrit :
> Hello,
>
> My keyboard and mouse don't work anymore with my Cyrus+ board with a FSL
> P50x0 PowerPC SoC [1] after the devicetree updates for 5.19 [2].
> After reverting the devicetree updates, my keyboard and mouse work
> without any problems.
> I figured out that the issue is in the patch for the file platform.c
> [3]. I created a patch for reverting the problematic code. (see
> attachment)
> After reverting the changes with the attached patch, the keyboard and
> mouse work again.
> Please check your changes in the file platform.c [3].
>
> Thanks,
> Christian
>
> [1] http://wiki.amiga.org/index.php?title=X5000
> [2]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86c87bea6b42100c67418af690919c44de6ede6e
>
> [3]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/drivers/of/platform.c?id=86c87bea6b42100c67418af690919c44de6ede6e
Based on your patch I would say the culprit commit is
https://github.com/torvalds/linux/commit/a1a2b7125e1079cfcc13a116aa3af3df2f9e002b
commit a1a2b7125e1079cfcc13a116aa3af3df2f9e002b
Author: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Date: Wed Mar 16 20:06:33 2022 +0000
of/platform: Drop static setup of IRQ resource from DT core
Now that all the DT drivers have switched to platform_get_irq() we
can now
safely drop the static setup of IRQ resource from DT core code.
With the above change hierarchical setup of irq domains is no longer
bypassed and thus allowing hierarchical interrupt domains to describe
interrupts using "interrupts" DT property.
Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Acked-by: Marc Zyngier <maz@kernel.org>
Tested-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Rob Herring <robh@kernel.org>
Link:
https://lore.kernel.org/r/20220316200633.28974-1-prabhakar.mahadev-lad.rj@bp.renesas.com
Can you please provide you device tree ?
Do you use any out-of-tree drivers ?
Thanks
Christophe
next prev parent reply other threads:[~2022-05-27 7:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 17:42 [FSL P50x0] Keyboard and mouse don't work anymore after the devicetree updates for 5.19 Christian Zigotzky
2022-05-27 7:23 ` Christophe Leroy [this message]
2022-05-27 7:48 ` Christian Zigotzky
2022-05-27 7:54 ` Fwd: " Christian Zigotzky
2022-05-27 7:56 ` Prabhakar Mahadev Lad
2022-05-27 8:06 ` Christian Zigotzky
2022-05-27 8:14 ` Prabhakar Mahadev Lad
2022-05-27 8:32 ` Christian Zigotzky
2022-05-27 14:23 ` Rob Herring
2022-05-28 8:05 ` Christian Zigotzky
2022-05-28 8:44 ` Christophe Leroy
2022-05-28 10:01 ` Christian Zigotzky
2022-05-30 5:26 ` Christian Zigotzky
2022-05-31 13:45 ` Rob Herring
2022-05-31 16:29 ` Christian Zigotzky
2022-06-01 12:35 ` Rob Herring
2022-06-04 13:12 ` Christian Zigotzky
2022-06-01 2:10 ` Christian Zigotzky
2022-06-06 14:58 ` Rob Herring
2022-06-06 16:13 ` Christian Zigotzky
2022-06-06 17:06 ` Rob Herring
2022-06-09 18:03 ` Christian Zigotzky
2022-06-13 15:57 ` Rob Herring
2022-06-16 17:04 ` Christian Zigotzky
-- strict thread matches above, loose matches on Subject: below --
2022-05-26 17:49 Christian Zigotzky
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=2e1b72bd-ae44-19d1-5981-09f5c69759dc@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rob.herring@calxeda.com \
--cc=rtd2@xtra.co.nz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).