linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override
Date: Thu, 4 May 2017 21:41:01 +0800	[thread overview]
Message-ID: <20170504134100.GR18578@dragon> (raw)
In-Reply-To: <4ba6bdf2-56b2-972d-3326-0eda3985c80b@denx.de>

On Thu, May 04, 2017 at 03:08:41PM +0200, Marek Vasut wrote:
> On 05/04/2017 02:44 PM, Shawn Guo wrote:
> > On Thu, May 04, 2017 at 12:06:11PM +0200, Marek Vasut wrote:

<snip>

> >> Mind you, my patch is not fixing any crash, it's correcting the
> >> regulator binding and removing the OPP override which is at that
> >> point useless.
> > 
> > Heh, that's the primary reason why I prefer Leonard's patch, as his
> > patch is fixing a critical crash issue, while yours is just removing
> > some useless stuff and correcting something that doesn't show any real
> > problem.
> 
> Maybe you want to compare those two patches again, his patch fixing the
> critical crash is removing the same "some useless stuff" as mine.

The difference is in commit message.  From your commit message, people
do not see what real world user noticeable issue your patch is fixing.

> Plus
> mine is actually making sure the regulators are configured correctly,
> not just removing "some useless stuff" and hoping for the best that
> bootloader will do the right thing.

Without this part, we do not get anything worse.  That said, it can be
an improvement in another patch.

> >> Which part of the following commit message is unclear?
> >>
> >> "
> >> The imx6sx-sdb has one power supply that drives both VDDARM_IN
> >> and VDDSOC_IN, which is the sw1a regulator on the PFUZE PMIC.
> >> Connect both inputs to the sw1a regulator on the PMIC and drop
> >> the OPP hackery which is no longer needed as the power framework
> >> will take care of the regulator configuration as needed.
> >> "
> > 
> > Something unclear in my opinion:
> > 
> >  - The OPP hackery was never needed, as it's only needed for LDO bypass
> >    mode which hasn't been supported by mainline kernel.  It's not 'no
> >    longer needed as the power framework ...'.
> 
> I don't know what this is about, it's not from my patch either ...

So I guess you do not understand how the OPP hackery was born and why it
shouldn't be there for mainline kernel at all.

> >  - What are the related changes in power framework?  It will be more
> >    clear if we can have the particular commit mentioned here.
> 
> Uh, I don't understand your question, there are no new changes in the
> power framework. The DT for the SDB was always wrong, my patch fixes it.

Then 'no longer needed' in your commit message is really confusing.

Shawn

  reply	other threads:[~2017-05-04 13:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 16:57 [PATCH] ARM: dts: imx6sx-sdb: Remove cpufreq OPP override Leonard Crestez
2017-04-25 17:02 ` Fabio Estevam
2017-04-25 17:02   ` Fabio Estevam
2017-04-25 17:23     ` Leonard Crestez
2017-04-25 17:26       ` Fabio Estevam
2017-04-25 17:28       ` Marek Vasut
2017-05-03 13:57         ` Shawn Guo
2017-05-03 14:26           ` Marek Vasut
2017-05-03 14:32             ` Marek Vasut
2017-05-03 14:41               ` Shawn Guo
2017-05-03 14:51                 ` Marek Vasut
2017-05-03 14:58             ` Leonard Crestez
2017-05-03 15:59               ` Marek Vasut
2017-05-03 17:58                 ` Leonard Crestez
2017-05-03 19:33                   ` Marek Vasut
2017-05-04  9:42                     ` Leonard Crestez
2017-05-04 10:06                       ` Marek Vasut
2017-05-04 12:44                         ` Shawn Guo
2017-05-04 13:08                           ` Marek Vasut
2017-05-04 13:41                             ` Shawn Guo [this message]
2017-05-04 14:34                               ` Marek Vasut
2017-05-05  1:18                                 ` Shawn Guo
2017-05-05 10:11                                   ` Leonard Crestez
2017-04-27  1:17 ` Peter Chen
2017-05-04 11:43   ` Shawn Guo
2017-05-04 11:46     ` Fabio Estevam
2017-05-04 12:50 ` Shawn Guo

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=20170504134100.GR18578@dragon \
    --to=shawnguo@kernel.org \
    --cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).