From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] arm: mecsbc: fixup /regulator-sd device tree node
Date: Fri, 5 Apr 2024 14:13:11 +0200 [thread overview]
Message-ID: <Zg_q11-0QnLLpXcm@pengutronix.de> (raw)
In-Reply-To: <09357d76-9bce-4087-ac93-4f4b4cf3c5f1@pengutronix.de>
On Fri, Apr 05, 2024 at 01:46:26PM +0200, Ahmad Fatoum wrote:
> Hello Sascha,
>
> On 05.04.24 12:12, Sascha Hauer wrote:
> > The MECSBC prototype board has a bug which makes the 1.8V SD mode
> > unusable. Add a fixup which sets the regulator-min-microvolt property of
> > the SD regulator to 3.3V to prevent the Kernel from going into 1.8V.
>
> Isn't that what the MMC no-1-8-v device tree property is for?
Although it's described in mmc-controller.yaml this is not a generic property.
Only SDHCI based controllers evaluate this property (which the affected
controller here isn't)
Sascha
>
> Cheers,
> Ahmad
>
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> > arch/arm/boards/protonic-mecsbc/board.c | 21 +++++++++++++++++++++
> > 1 file changed, 21 insertions(+)
> >
> > diff --git a/arch/arm/boards/protonic-mecsbc/board.c b/arch/arm/boards/protonic-mecsbc/board.c
> > index 3ba8fb8d1c..56f7ca393a 100644
> > --- a/arch/arm/boards/protonic-mecsbc/board.c
> > +++ b/arch/arm/boards/protonic-mecsbc/board.c
> > @@ -90,6 +90,24 @@ static void mecsbc_process_adc(struct device *dev)
> > pr_info("VIN = %d V\n", mecsbc_get_vin_mv() / 1000);
> > }
> >
> > +static int mecsbc_sd_of_fixup(struct device_node *root, void *context)
> > +{
> > + struct device *dev = context;
> > + struct device_node *np;
> > +
> > + dev_info(dev, "Fixing up /regulator-sd\n");
> > +
> > + np = of_find_node_by_path_from(root, "/regulator-sd");
> > + if (!np) {
> > + dev_err(dev, "Cannot find /regulator-sd node\n");
> > + return 0;
> > + }
> > +
> > + of_property_write_u32(np, "regulator-min-microvolt", 3300000);
> > +
> > + return 0;
> > +}
> > +
> > static int mecsbc_of_fixup_hwrev(struct device *dev)
> > {
> > const char *compat;
> > @@ -103,6 +121,9 @@ static int mecsbc_of_fixup_hwrev(struct device *dev)
> >
> > free(buf);
> >
> > + if (mecsbc_data.hw_id == 0 && mecsbc_data.hw_rev == 0)
> > + of_register_fixup(mecsbc_sd_of_fixup, dev);
> > +
> > return 0;
> > }
> >
>
> --
> Pengutronix e.K. | |
> Steuerwalder Str. 21 | http://www.pengutronix.de/ |
> 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
> Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-04-05 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 10:12 Sascha Hauer
2024-04-05 11:46 ` Ahmad Fatoum
2024-04-05 12:13 ` Sascha Hauer [this message]
2024-04-08 6:50 ` Sascha Hauer
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=Zg_q11-0QnLLpXcm@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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