Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: linux-omap@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"H. Nikolaus Schaller" <hns@goldelico.com>,
	Sicelo Mhlongo <absicsz@gmail.com>
Subject: [PATCH 0/3] Update musb to probe with ti-sysc for omap3
Date: Fri, 18 Nov 2022 12:42:23 +0200	[thread overview]
Message-ID: <20221118104226.46223-1-tony@atomide.com> (raw)

Hi all,

After fixing the probe issues with [0], let's update omap3 to use ti-sysc
for musb so the driver behaves the same way for all the SoCs.

Regards,

Tony

[0] https://lore.kernel.org/linux-usb/20221118102532.34458-1-tony@atomide.com/T/#u

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(-)

-- 
2.38.1

             reply	other threads:[~2022-11-18 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 10:42 Tony Lindgren [this message]
2022-11-18 10:42 ` [PATCH 1/3] bus: ti-sysc: Add otg quirk flags for omap3 musb Tony Lindgren
2022-11-19  4:09   ` Sicelo
2022-11-18 10:42 ` [PATCH 2/3] ARM: dts: Update omap3 musb to probe with ti-sysc Tony Lindgren
2022-11-19  4:11   ` Sicelo
2022-11-18 10:42 ` [PATCH 3/3] ARM: OMAP2+: Drop legacy hwmod data for omap3 otg Tony Lindgren
2022-11-19  4:12   ` Sicelo

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=20221118104226.46223-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=absicsz@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hns@goldelico.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox