From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Devicetree related musb changes for omap3 for v6.2
Date: Fri, 25 Nov 2022 10:23:12 +0200 [thread overview]
Message-ID: <pull-1669364566-84575@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/musb-for-v6.2-signed
for you to fetch changes up to 42a79edd4a3dc1bb8e89fd2849f9e8e1e1c13977:
ARM: OMAP2+: Drop legacy hwmod data for omap3 otg (2022-11-22 13:25:20 +0200)
----------------------------------------------------------------
Devicetree related musb changes for omap3 for v6.2
Recent musb driver regressions eposed two issues for musb legacy
probing. The changes to use device_set_of_node_from_dev() confuse
the legacy interconnect code. And we now have to manually populate
the musb core irq resources.
The musb driver has a fix for these, but it's not a good long term
solution. To fix the issue properly, let's just update musb to
probe with ti-sysc interconnect driver with proper devicetree data.
This allows dropping most of the musb driver workaround later on.
And with these changes we have the omap2430 musb glue layer behaving
the same way for all the SoCs using it.
We need to patch the ti-sysc driver quirks, and add devicetree
data to make things work. And we want to drop the legacy data too
to avoid pointless warnings.
As we have a musb driver workaround, these changes are not needed as
fixes and can wait for the merge window.
----------------------------------------------------------------
Tony Lindgren (3):
bus: ti-sysc: Add otg quirk flags for omap3 musb
ARM: dts: Update omap3 musb to probe with ti-sysc
ARM: OMAP2+: Drop legacy hwmod data for omap3 otg
arch/arm/boot/dts/am3517.dtsi | 38 +++++++++---
arch/arm/boot/dts/omap3.dtsi | 40 +++++++++---
arch/arm/boot/dts/omap34xx.dtsi | 4 ++
arch/arm/boot/dts/omap36xx.dtsi | 4 ++
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 99 ------------------------------
drivers/bus/ti-sysc.c | 6 ++
6 files changed, 75 insertions(+), 116 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Tony Lindgren" <tony@atomide.com>
Subject: [GIT PULL] Devicetree related musb changes for omap3 for v6.2
Date: Fri, 25 Nov 2022 10:23:12 +0200 [thread overview]
Message-ID: <pull-1669364566-84575@atomide.com> (raw)
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/musb-for-v6.2-signed
for you to fetch changes up to 42a79edd4a3dc1bb8e89fd2849f9e8e1e1c13977:
ARM: OMAP2+: Drop legacy hwmod data for omap3 otg (2022-11-22 13:25:20 +0200)
----------------------------------------------------------------
Devicetree related musb changes for omap3 for v6.2
Recent musb driver regressions eposed two issues for musb legacy
probing. The changes to use device_set_of_node_from_dev() confuse
the legacy interconnect code. And we now have to manually populate
the musb core irq resources.
The musb driver has a fix for these, but it's not a good long term
solution. To fix the issue properly, let's just update musb to
probe with ti-sysc interconnect driver with proper devicetree data.
This allows dropping most of the musb driver workaround later on.
And with these changes we have the omap2430 musb glue layer behaving
the same way for all the SoCs using it.
We need to patch the ti-sysc driver quirks, and add devicetree
data to make things work. And we want to drop the legacy data too
to avoid pointless warnings.
As we have a musb driver workaround, these changes are not needed as
fixes and can wait for the merge window.
----------------------------------------------------------------
Tony Lindgren (3):
bus: ti-sysc: Add otg quirk flags for omap3 musb
ARM: dts: Update omap3 musb to probe with ti-sysc
ARM: OMAP2+: Drop legacy hwmod data for omap3 otg
arch/arm/boot/dts/am3517.dtsi | 38 +++++++++---
arch/arm/boot/dts/omap3.dtsi | 40 +++++++++---
arch/arm/boot/dts/omap34xx.dtsi | 4 ++
arch/arm/boot/dts/omap36xx.dtsi | 4 ++
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 99 ------------------------------
drivers/bus/ti-sysc.c | 6 ++
6 files changed, 75 insertions(+), 116 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-25 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 8:23 Tony Lindgren [this message]
2022-11-25 8:23 ` [GIT PULL] Devicetree related musb changes for omap3 for v6.2 Tony Lindgren
2022-11-30 17:11 ` patchwork-bot+linux-soc
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=pull-1669364566-84575@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@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.