From: "Timo Sigurdsson" <public_timo.s@silentcreek.de>
To: maxime.ripard@free-electrons.com
Cc: hdegoede@redhat.com, wens@csie.org, galak@codeaurora.org,
linux-kernel@vger.kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, ijc+devicetree@hellion.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@googlegroups.com, pawel.moll@arm.com,
linux@arm.linux.org.uk, robh+dt@kernel.org
Subject: Re: [linux-sunxi] [RFC] ARM: dts: sunxi: Add regulators and board-specific operating points for LeMaker BananaPi
Date: Tue, 28 Jul 2015 17:01:23 +0200 (CEST) [thread overview]
Message-ID: <20150728150123.1AAA46C86538@dd34104.kasserver.com> (raw)
In-Reply-To: <20150728125545.GC2564@lukather>
Hi,
Maxime Ripard schrieb am 28.07.2015 14:55:
>> IMHO for a common maximum opp that's a good approach. But for the lowest
>> frequency setting, it would seem more logical to me, to raise the voltage
>> to a point where all boards will run fine with them, unless those boards
>> cannot handle the frequency regardless of the higher voltage.
>
> Agreed.
Ok, then I will write another patch for this as well, unless Chen-Yu or
someone else objects.
Regards,
Timo
prev parent reply other threads:[~2015-07-28 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 1:28 Timo Sigurdsson
2015-07-27 8:07 ` [linux-sunxi] " Hans de Goede
2015-07-27 12:09 ` public_timo.s
2015-07-27 12:43 ` Hans de Goede
2015-07-28 9:02 ` Timo Sigurdsson
2015-07-28 12:55 ` Maxime Ripard
2015-07-28 14:57 ` Timo Sigurdsson
2015-07-28 12:49 ` Maxime Ripard
2015-07-28 14:24 ` Hans de Goede
2015-07-28 15:09 ` Timo Sigurdsson
2015-07-28 15:29 ` Hans de Goede
2015-08-02 22:00 ` Timo Sigurdsson
2015-07-28 14:45 ` Timo Sigurdsson
2015-07-27 12:36 ` public_timo.s
2015-07-27 12:54 ` Hans de Goede
[not found] ` <CAGb2v65ApKvrj6K+kw43u=0q6=auTsmQjCXhibgZkW+vd5nDqA@mail.gmail.com>
2015-07-28 9:02 ` Timo Sigurdsson
2015-07-28 12:55 ` Maxime Ripard
2015-07-28 15:01 ` 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=20150728150123.1AAA46C86538@dd34104.kasserver.com \
--to=public_timo.s@silentcreek.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hdegoede@redhat.com \
--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®