From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: Alexandre Ghiti <alexandre.ghiti@canonical.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Pragnesh Patel <pragnesh.patel@sifive.com>,
Green Wan <green.wan@sifive.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH] drivers: pmic: Add sysreset driver to da9063 pmic device
Date: Tue, 21 Sep 2021 09:23:50 +0200 [thread overview]
Message-ID: <396c1517-b871-5768-40f8-8e312879041f@canonical.com> (raw)
In-Reply-To: <20210920154809.1695453-1-alexandre.ghiti@canonical.com>
On 9/20/21 5:48 PM, Alexandre Ghiti wrote:
> This pmic device is present on the SiFive Unmatched board and this
> new driver adds the possibility to reset it.
>
> Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
> ---
> configs/sifive_unmatched_defconfig | 2 ++
> drivers/power/pmic/da9063.c | 49 ++++++++++++++++++++++++++++++
> 2 files changed, 51 insertions(+)
>
> diff --git a/configs/sifive_unmatched_defconfig b/configs/sifive_unmatched_defconfig
> index 978818b688..9ab058be39 100644
> --- a/configs/sifive_unmatched_defconfig
> +++ b/configs/sifive_unmatched_defconfig
> @@ -43,3 +43,5 @@ CONFIG_DM_USB=y
> CONFIG_USB_XHCI_HCD=y
> CONFIG_USB_XHCI_PCI=y
> CONFIG_BOARD_EARLY_INIT_F=y
> +CONFIG_DM_PMIC=y
> +CONFIG_DM_PMIC_DA9063=y
> diff --git a/drivers/power/pmic/da9063.c b/drivers/power/pmic/da9063.c
> index 25101d18f7..b04879d9c5 100644
> --- a/drivers/power/pmic/da9063.c
> +++ b/drivers/power/pmic/da9063.c
> @@ -10,6 +10,7 @@
> #include <dm.h>
> #include <i2c.h>
> #include <log.h>
> +#include <dm/lists.h>
> #include <power/pmic.h>
> #include <power/regulator.h>
> #include <power/da9063_pmic.h>
> @@ -87,6 +88,7 @@ static int da9063_bind(struct udevice *dev)
> {
> ofnode regulators_node;
> int children;
> + int ret;
>
> regulators_node = dev_read_subnode(dev, "regulators");
> if (!ofnode_valid(regulators_node)) {
> @@ -101,6 +103,14 @@ static int da9063_bind(struct udevice *dev)
> if (!children)
> debug("%s: %s - no child found\n", __func__, dev->name);
>
> + if (CONFIG_IS_ENABLED(SYSRESET)) {
Thank you for addressing the missing reset driver for the SiFive
Unmatched board.
I imagine some existing or future boards using the DA9063 will have a
GPIO for system reset. Should all boards having a DA9063 PMIC implement
system reset via the power management IC?
We could instead use the devicetree to identify if a board shall use the
DA9063 for system reset.
> + ret = device_bind_driver(dev, "da9063-sysreset",
> + "da9063-sysreset", NULL);
> + if (ret)
> + debug("%s: %s - failed to bind sysreset driver\n",
> + __func__, dev->name);
> + }
> +
> /* Always return success for this device */
> return 0;
> }
> @@ -129,3 +139,42 @@ U_BOOT_DRIVER(pmic_da9063) = {
> .probe = da9063_probe,
> .ops = &da9063_ops,
> };
> +
> +#ifdef CONFIG_SYSRESET
The linker will remove functions that are not used automatically. We
have tended to not enclose functions in #ifdef but instead allow the
compiler to check the code.
> +#include <sysreset.h>
Please, keep includes at the top of the code.
> +
Even though this is a static function I would add a Sphinx style comment
here. Cf.
https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html#function-documentation
Best regards
Heinrich
> +static int da9063_sysreset_request(struct udevice *dev, enum sysreset_t type)
> +{
> + struct udevice *pmic_dev = dev->parent;
> + uint ret;
> +
> + if (type != SYSRESET_WARM && type != SYSRESET_COLD)
> + return -EPROTONOSUPPORT;
> +
> + ret = pmic_reg_write(pmic_dev, DA9063_REG_PAGE_CON, 0x00);
> + if (ret < 0)
> + return ret;
> +
> + /* Sets the WAKE_UP bit */
> + ret = pmic_reg_write(pmic_dev, DA9063_REG_CONTROL_F, 0x04);
> + if (ret < 0)
> + return ret;
> +
> + /* Powerdown! */
> + ret = pmic_reg_write(pmic_dev, DA9063_REG_CONTROL_A, 0x68);
> + if (ret < 0)
> + return ret;
> +
> + return -EINPROGRESS;
> +}
> +
> +static struct sysreset_ops da9063_sysreset_ops = {
> + .request = da9063_sysreset_request,
> +};
> +
> +U_BOOT_DRIVER(da9063_sysreset) = {
> + .name = "da9063-sysreset",
> + .id = UCLASS_SYSRESET,
> + .ops = &da9063_sysreset_ops,
> +};
> +#endif
>
next prev parent reply other threads:[~2021-09-21 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210920154820epcas1p3088b204ad0e5fb1d203affd867be2835@epcas1p3.samsung.com>
2021-09-20 15:48 ` [PATCH] drivers: pmic: Add sysreset driver to da9063 pmic device Alexandre Ghiti
2021-09-21 7:23 ` Heinrich Schuchardt [this message]
2021-09-22 7:13 ` Alexandre Ghiti
2021-09-23 12:23 ` Jaehoon Chung
2021-09-24 8:45 ` Alexandre Ghiti
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=396c1517-b871-5768-40f8-8e312879041f@canonical.com \
--to=heinrich.schuchardt@canonical.com \
--cc=alexandre.ghiti@canonical.com \
--cc=green.wan@sifive.com \
--cc=jh80.chung@samsung.com \
--cc=paul.walmsley@sifive.com \
--cc=pragnesh.patel@sifive.com \
--cc=u-boot@lists.denx.de \
/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.