From: Rob Herring <robh@kernel.org>
To: Matthias Brugger <matthias.bgg@gmail.com>, Bin Liu <b-liu@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Paul Cercueil <paul@crapouillou.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: [PATCH 0/2] usb: musb resource clean-ups
Date: Wed, 15 Dec 2021 17:07:55 -0600 [thread overview]
Message-ID: <20211215230756.2009115-1-robh@kernel.org> (raw)
This short series reworks the platform device resources of the musb
child device to avoid using static resources. Setting the parent
device's DT node on the child device is sufficient for the standard
resource functions to work.
I ran this thru kernel-ci and didn't see any failures, but I don't know
if any tested platform uses MUSB driver or if a failure would show up in
the boot log.
Rob
Rob Herring (2):
usb: musb: Drop unneeded resource copying
usb: musb: Set the DT node on the child device
drivers/usb/musb/am35x.c | 2 ++
drivers/usb/musb/da8xx.c | 20 ++++----------------
drivers/usb/musb/jz4740.c | 1 +
drivers/usb/musb/mediatek.c | 2 ++
drivers/usb/musb/omap2430.c | 23 ++---------------------
drivers/usb/musb/ux500.c | 18 ++----------------
6 files changed, 13 insertions(+), 53 deletions(-)
--
2.32.0
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next reply other threads:[~2021-12-15 23:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 23:07 Rob Herring [this message]
2021-12-15 23:07 ` [PATCH 1/2] usb: musb: Drop unneeded resource copying Rob Herring
2021-12-15 23:07 ` [PATCH 2/2] usb: musb: Set the DT node on the child device Rob Herring
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=20211215230756.2009115-1-robh@kernel.org \
--to=robh@kernel.org \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=paul@crapouillou.net \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
/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).