From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: marek.vasut+renesas@gmail.com, lee.jones@linaro.org,
matti.vaittinen@fi.rohmeurope.com, lgirdwood@gmail.com,
broonie@kernel.org, linus.walleij@linaro.org,
bgolaszewski@baylibre.com
Cc: khiem.nguyen.xt@renesas.com, linux-power@fi.rohmeurope.com,
linux-gpio@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: [PATCH v9 00/12] treewide: bd9571mwv: Add support for BD9574MWF
Date: Tue, 12 Jan 2021 18:00:55 +0900 [thread overview]
Message-ID: <1610442067-7446-1-git-send-email-yoshihiro.shimoda.uh@renesas.com> (raw)
Add BD9574MWF support into bd9571mwv gpio, mfd and regulator drivers.
Latest Ebisu-4D boards has this chip instead of BD9571MWV so that
we need this patch series to detect this chip at runtime.
Note that the patch [1/12] is a bug-fix patch for mfd driver.
Hello Lee,
Now I got Acked-by from maintainers of gpio and regulator. So,
would you apply this series to your repo?
Changes from v8:
- Add Acked-by from maintainers of regulator and gpio in patch 4 to 8.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=406323
Changes from v7:
- Fix typo in the patch 10.
- Add "Acked-for-MFD-by" in patch 2 and 11.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=406091
Changes from v6:
- Remove "struct bd957x_ddata" because this is not used after probed.
- Add "Acked-for-MFD-by" in patch 12.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=405725
Changes from v5:
- Fix typo in the patch 5 and 8.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=405263
Changes from v4:
- Add Reviwed-by in patch 1, 10, 11 and 12.
- Keep bd9571mwv_id_table[] as-is because unused in patch 12.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=404657
Changes from v3:
- Add "Acked-for-MFD-by" in patch 1, 3, 9 and 10.
- Use "Co-developed-by" instead in patch 11.
- In patch 11:
-- Remove abusing kernel-doc formatting in patch.
-- Rename bd957x_data with bd957x_ddata in patch.
-- Remove product name printk.
-- Rename bd9571mwv_identify() with bd957x_identify().
-- Remove argument "part_name" from bd957x_identify().
-- Modify dev_err() string.
-- Rename BD9571MWV_PRODUCT_CODE_VAL with BD9571MWV_PRODUCT_CODE_BD9571MWV.
-- Fix errno from -ENOENT to -ENODEV.
- In patch 12:
-- Rename "MFD driver" to "core driver".
-- Remove unnecessary comments.
-- Rename BD9574MWF_PRODUCT_CODE_VAL with BD9571MWV_PRODUCT_CODE_BD9574MWF.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=402719
Changes from v2:
- Use devm_mfd_add_devices() to remove the mfd device in unload.
- Update commit descriptions in patch 4 and 8.
- Use regmap_get_device() to simplify in patch 4.
- Remove "struct bd9571mwv" and bd9571mwv_remove().
- Add Reviewed-by in patch 3 to 9.
- Use devm_regmap_add_irq_chip() to simplify in patch 10.
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=400477
Changes from v1:
- Document BD9574MWF on the dt-binding.
- Add ROHM_CHIP_TYPE_BD957[14] into rohm-generic.h.
- To simplify gpio and regulator drivers, using regmap instead of
using struct bd9571mwv.
- Remove BD9574MWF definitions to make gpio and regulator driver
simple to support for BD9574MWF.
- Add BD9574MWF support for gpio and regulator drivers.
- Add missing regmap ranges for BD9574MWF.
- Rename "part_number" with "part_name".
https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=398059
Khiem Nguyen (2):
mfd: bd9571mwv: Make the driver more generic
mfd: bd9571mwv: Add support for BD9574MWF
Yoshihiro Shimoda (10):
mfd: bd9571mwv: Use devm_mfd_add_devices()
dt-bindings: mfd: bd9571mwv: Document BD9574MWF
mfd: rohm-generic: Add BD9571 and BD9574
regulator: bd9571mwv: rid of using struct bd9571mwv
regulator: bd9571mwv: Add BD9574MWF support
gpio: bd9571mwv: Use the SPDX license identifier
gpio: bd9571mwv: rid of using struct bd9571mwv
gpio: bd9571mwv: Add BD9574MWF support
mfd: bd9571mwv: Use the SPDX license identifier
mfd: bd9571mwv: Use devm_regmap_add_irq_chip()
.../devicetree/bindings/mfd/bd9571mwv.txt | 4 +-
drivers/gpio/gpio-bd9571mwv.c | 35 ++--
drivers/mfd/bd9571mwv.c | 178 ++++++++++++++-------
drivers/regulator/bd9571mwv-regulator.c | 59 ++++---
include/linux/mfd/bd9571mwv.h | 45 ++----
include/linux/mfd/rohm-generic.h | 2 +
6 files changed, 186 insertions(+), 137 deletions(-)
--
2.7.4
next reply other threads:[~2021-01-12 9:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 9:00 Yoshihiro Shimoda [this message]
2021-01-12 9:00 ` [PATCH v9 01/12] mfd: bd9571mwv: Use devm_mfd_add_devices() Yoshihiro Shimoda
2021-01-12 9:00 ` [PATCH v9 02/12] dt-bindings: mfd: bd9571mwv: Document BD9574MWF Yoshihiro Shimoda
2021-01-12 9:00 ` [PATCH v9 03/12] mfd: rohm-generic: Add BD9571 and BD9574 Yoshihiro Shimoda
2021-01-12 9:00 ` [PATCH v9 04/12] regulator: bd9571mwv: rid of using struct bd9571mwv Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 05/12] regulator: bd9571mwv: Add BD9574MWF support Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 06/12] gpio: bd9571mwv: Use the SPDX license identifier Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 07/12] gpio: bd9571mwv: rid of using struct bd9571mwv Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 08/12] gpio: bd9571mwv: Add BD9574MWF support Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 09/12] mfd: bd9571mwv: Use the SPDX license identifier Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 10/12] mfd: bd9571mwv: Use devm_regmap_add_irq_chip() Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 11/12] mfd: bd9571mwv: Make the driver more generic Yoshihiro Shimoda
2021-01-12 9:01 ` [PATCH v9 12/12] mfd: bd9571mwv: Add support for BD9574MWF Yoshihiro Shimoda
2021-01-14 13:08 ` [GIT PULL] Immutable branch between MFD, GPIO and Regulator due for the v5.12 merge window Lee Jones
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=1610442067-7446-1-git-send-email-yoshihiro.shimoda.uh@renesas.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=khiem.nguyen.xt@renesas.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-power@fi.rohmeurope.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.com \
--cc=matti.vaittinen@fi.rohmeurope.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).