mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Timo Sigurdsson" <public_timo.s@silentcreek.de>
To: maxime.ripard@free-electrons.com
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	linux@arm.linux.org.uk, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com,
	wens@csie.org
Subject: Re: [PATCH] ARM: dts: sunxi: Raise minimum CPU voltage for sun7i-a20 to a level all boards can supply
Date: Tue,  4 Aug 2015 10:38:19 +0200 (CEST)	[thread overview]
Message-ID: <20150804083819.2F3EE6C83EF9@dd34104.kasserver.com> (raw)
In-Reply-To: <20150803091300.GY2564@lukather>

Hi Maxime,

Maxime Ripard schrieb am 03.08.2015 11:13:
> On Sun, Aug 02, 2015 at 09:23:06PM +0200, Timo Sigurdsson wrote:
>> sun7i-a20.dtsi contains an cpufreq operating point at 0.9 volts. Most A20
>> boards
>> (or all?), however, do not allow the voltage to go below 1.0V. Thus, raise the
>> voltage for the lowest operating point to 1.0V so all boards can actually use
>> it.
> 
> This is not a property of a board, but is the actual limit documented
> by Allwinner for the A20. Some individual SoCs might have wider
> tolerances, but that's not a property of a board, it's really a
> property of a single SoC, and we cannot make any assumption on the
> board.

Thanks for the clarification. That was a misunderstanding on my side. I can 
update the commit message in a second version of the patch, but the actual
code change can be kept as is then, I guess.

> (and please make sure to run checkpatch before sending your patches)

Sorry about that. Will do when I post a second version of the patch.

Thanks,

Timo

      reply	other threads:[~2015-08-04  8:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02 19:23 Timo Sigurdsson
2015-08-02 23:35 ` [linux-sunxi] " Julian Calaby
2015-08-03  2:37   ` Chen-Yu Tsai
2015-08-03  4:22     ` Julian Calaby
2015-08-03  4:26       ` Chen-Yu Tsai
2015-08-03  9:03       ` Timo Sigurdsson
2015-08-03  9:34         ` Maxime Ripard
2015-08-03  9:36           ` Julian Calaby
2015-08-04  8:51           ` Timo Sigurdsson
2015-08-03  9:28       ` Maxime Ripard
2015-08-03  8:37   ` Timo Sigurdsson
2015-08-03  9:23     ` Maxime Ripard
2015-08-03  9:16   ` Maxime Ripard
2015-08-03  9:13 ` Maxime Ripard
2015-08-04  8:38   ` Timo Sigurdsson [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=20150804083819.2F3EE6C83EF9@dd34104.kasserver.com \
    --to=public_timo.s@silentcreek.de \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@googlegroups.com \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=wens@csie.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
all inboxes | Powered by JetHome®