From: Tony Lindgren <tony@atomide.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Keerthy <j-keerthy@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
galak@codeaurora.org, mark.rutland@arm.com, pawel.moll@arm.com
Subject: Re: [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage
Date: Mon, 10 Nov 2014 09:05:51 -0800 [thread overview]
Message-ID: <20141110170550.GL31454@atomide.com> (raw)
In-Reply-To: <CAOCHtYiT9VgXD73gLRszSquJsN0Ew1KSNk_tXpA5OcDkT7KnqQ@mail.gmail.com>
* Robert Nelson <robertcnelson@gmail.com> [141106 11:31]:
> On Thu, Nov 6, 2014 at 12:25 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Keerthy <j-keerthy@ti.com> [141106 02:55]:
> >> Fix DCDC3 volatge to 1.5V which is the right value to be supplied by
> >> DCDC3 for all the boards.
> >
> > Hmm so what about the comments for similar beaglebone changes
> > in thread "[PATCH] ARM: dts: am335x-boneblack: set dcdc1 regulator
> > for 1.35v ddr3"?
>
> Based on Keerthy's patchset, i think we should just ignore my "1.35v"
> ddr3 patch for the beaglebone black. As by default it will be at
> 1.50v. (so we can either define it for clarity at 1.50v or just ignore
> it.)
OK thanks. I'll apply these into omap-for-v3.18/fixes and ignore
your beaglebone black patch.
Regards,
Tony
next prev parent reply other threads:[~2014-11-10 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 10:50 [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage Keerthy
2014-11-06 10:50 ` [PATCH 1/3] ARM: dts: AM43x-EPOS-EVM: Fix DCDC3 voltage Keerthy
2014-11-06 10:50 ` [PATCH 2/3] ARM: dts: AM437x-GP-EVM: " Keerthy
2014-11-06 10:50 ` [PATCH 3/3] ARM: dts: AM437x-SK-EVM: " Keerthy
2014-11-06 13:45 ` [PATCH 0/3] ARM: dts: AM43x: Fix DCDC3 regulator voltage Nishanth Menon
2014-11-06 18:25 ` Tony Lindgren
2014-11-06 19:29 ` Robert Nelson
2014-11-07 5:26 ` Keerthy
2014-11-07 5:30 ` Keerthy
2014-11-10 17:05 ` Tony Lindgren [this message]
[not found] ` <20141106182526.GC31454-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-11-07 4:46 ` Keerthy
2014-11-07 8:38 ` Keerthy
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=20141110170550.GL31454@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=j-keerthy@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robertcnelson@gmail.com \
/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).