All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: "Stefan Riedmüller" <s.riedmueller@phytec.de>
Cc: festevam@gmail.com, shawnguo@kernel.org,
	chf.fritz@googlemail.com, robh+dt@kernel.org, linux-imx@nxp.com,
	kernel@pengutronix.de, c.hemp@phytec.de, s.christ@phytec.de,
	linux-arm-kernel@lists.infradead.org,
	Lucas Stach <l.stach@pengutronix.de>
Subject: Re: [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage
Date: Thu, 5 Dec 2019 08:19:34 +0100	[thread overview]
Message-ID: <20191205071934.fkslkkkjuwrnxmbt@pengutronix.de> (raw)
In-Reply-To: <21bdac21-d5e0-ea84-57b4-5998f64899e9@phytec.de>

Hi Stefan,

On 19-12-03 13:37, Stefan Riedmüller wrote:
> Hi Lucas, hi Marco,
> 
> On 03.12.19 12:44, Lucas Stach wrote:

...

> > 
> > The DT constraints are supposed to reflect absolute maximum ratings of
> > the board design. The regulator driver already knows the limits of the
> > PMIC chip, so there is no point in duplicating this information in the
> > DT.
> > 
> > The DT constraints are there to make sure the regulator core can
> > constrain the voltage setting to something safe for the specific
> > design. A consumer driver bug must never be able to set a voltage that
> > is outside of the absolute maximum ratings of _all_ consumers of this
> > specific power rail. I know that a lot of DTs get this detail wrong,
> > but we shouldn't block patches to fix this. :)
> 
> Thanks for the clarification and the example. I got it now and will keep it
> in mind for the future.
> 
> > 
> > > > If I have this wrong and the maintainers agree with you could you please
> > > > make sure to account for the bypass mode as well since these values from the
> > > > datasheet are valid too?
> > > 
> > > As I said, the bypass mode isn't supported by the driver and all imx6
> > > based devicetrees follow that case. So we don't have to take that into
> > > account. Also we can't meet both contraints with one dt and futhermore
> > > the bypass mode decrease your imx6 lifetime due the the increased ripple
> > > on the arm-core supply. So I think no one wants this setup in the near
> > > future.
> > 
> > As a violation of the minimum voltage setting is very unlikely to cause
> > any permanent damage to the design (expect if you got reverse voltage
> > flows somewhere) I think it is safe to include the LDO bypass supply
> > limits as the lower bound in the DT constraints, even if this mode
> > isn't currently used anywhere.
> 
> Sounds good to me.

Okay, I will use the bypass value and add a comment. Stefan can you take
a look at the other patches as well?

Regards,
  Marco

> Regards,
> Stefan
> 
> > 
> > Regards,
> > Lucas
> > 
> 

-- 
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 |

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2019-12-05  7:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-29 16:48 [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Marco Felsch
2019-11-29 16:48 ` [PATCH 2/3] ARM: dts: imx6: phycore-som: fix emmc supply Marco Felsch
2019-12-05 12:00   ` Stefan Riedmüller
2019-12-10  9:09     ` Marco Felsch
2019-12-12  9:00       ` Stefan Riedmüller
2019-11-29 16:48 ` [PATCH 3/3] ARM: dts: imx6: phycore-som: add pmic onkey device Marco Felsch
2020-01-07 13:48   ` Marco Felsch
2020-01-09  6:46   ` Shawn Guo
2019-12-02 10:09 ` [PATCH 1/3] ARM: dts: imx6: phycore-som: fix arm and soc minimum voltage Stefan Riedmüller
2019-12-02 12:42   ` Marco Felsch
2019-12-02 13:55     ` Stefan Riedmüller
2019-12-02 14:14       ` Marco Felsch
2019-12-02 14:30         ` Stefan Riedmüller
2019-12-02 14:53           ` Marco Felsch
2019-12-03  8:11             ` Stefan Riedmüller
2019-12-03  8:33               ` Marco Felsch
2019-12-03  9:07                 ` Stefan Riedmüller
2019-12-03 11:44                 ` Lucas Stach
2019-12-03 12:37                   ` Stefan Riedmüller
2019-12-05  7:19                     ` Marco Felsch [this message]

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=20191205071934.fkslkkkjuwrnxmbt@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=c.hemp@phytec.de \
    --cc=chf.fritz@googlemail.com \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.christ@phytec.de \
    --cc=s.riedmueller@phytec.de \
    --cc=shawnguo@kernel.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 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.