From: Dejin Zheng <zhengdejin5@gmail.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org,
hminas@synopsys.com, mathias.nyman@intel.com,
bgolaszewski@baylibre.com, arnd@arndb.de,
geert+renesas@glider.be, tomas.winkler@intel.com,
tglx@linutronix.de, hdegoede@redhat.com, treding@nvidia.com,
suzuki.poulose@arm.com
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Dejin Zheng <zhengdejin5@gmail.com>
Subject: [PATCH v4 0/5] drivers: new helper for ioremapping memory resources
Date: Tue, 24 Mar 2020 00:06:07 +0800 [thread overview]
Message-ID: <20200323160612.17277-1-zhengdejin5@gmail.com> (raw)
Since commit "drivers: provide devm_platform_ioremap_resource()",
It was wrap platform_get_resource() and devm_ioremap_resource() as
single helper devm_platform_ioremap_resource(). but now, many drivers
still used platform_get_resource() and devm_ioremap_resource()
together in the kernel tree. The reason can not be replaced is they
still need use the resource variables obtained by platform_get_resource().
so provide this helper.
The first patch in this series adds a wrapper for these two calls and
the other uses it in a driver.
v3 -> v4:
- modified the description of a parameter res in patch 1.
- modified patch 5's commit comment.
v2 -> v3:
- rename the function to
devm_platform_get_and_ioremap_resource() by Sergei's suggestion.
- make the last parameter res as optional by Geert's suggestion.
- Reimplement devm_platform_ioremap_resource by calling
devm_platform_get_and_ioremap_resource() by Geert's suggestion.
v1 -> v2:
- add some real users of this function (Thanks for greg k-h's reminder)
Dejin Zheng (5):
drivers: provide devm_platform_get_and_ioremap_resource()
usb: host: xhci-plat: convert to
devm_platform_get_and_ioremap_resource
usb: host: hisilicon: convert to
devm_platform_get_and_ioremap_resource
usb: dwc2: convert to devm_platform_get_and_ioremap_resource
driver core: platform: Reimplement devm_platform_ioremap_resource
drivers/base/platform.c | 27 +++++++++++++++++++++++----
drivers/usb/dwc2/platform.c | 3 +--
drivers/usb/host/xhci-histb.c | 3 +--
drivers/usb/host/xhci-plat.c | 3 +--
include/linux/platform_device.h | 3 +++
5 files changed, 29 insertions(+), 10 deletions(-)
--
2.25.0
next reply other threads:[~2020-03-23 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 16:06 Dejin Zheng [this message]
2020-03-23 16:06 ` [PATCH v4 1/5] drivers: provide devm_platform_get_and_ioremap_resource() Dejin Zheng
2020-03-23 16:06 ` [PATCH v4 2/5] usb: host: xhci-plat: convert to devm_platform_get_and_ioremap_resource Dejin Zheng
2020-03-23 16:06 ` [PATCH v4 3/5] usb: host: hisilicon: " Dejin Zheng
2020-03-23 16:06 ` [PATCH v4 4/5] usb: dwc2: " Dejin Zheng
2020-03-23 16:06 ` [PATCH v4 5/5] driver core: platform: Reimplement devm_platform_ioremap_resource Dejin Zheng
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=20200323160612.17277-1-zhengdejin5@gmail.com \
--to=zhengdejin5@gmail.com \
--cc=arnd@arndb.de \
--cc=bgolaszewski@baylibre.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=hminas@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=rafael@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tglx@linutronix.de \
--cc=tomas.winkler@intel.com \
--cc=treding@nvidia.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).