From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tom Rini <trini@ti.com>,
balbi@ti.com, devicetree@vger.kernel.org,
beagleboard@googlegroups.com, linux-kernel@vger.kernel.org,
gerald@granddesignsgroup.com, fcooper@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: Add am57xx-beagle-x15
Date: Thu, 6 Nov 2014 10:53:19 -0600 [thread overview]
Message-ID: <545BA77F.2080609@ti.com> (raw)
In-Reply-To: <20141106164843.GY31454@atomide.com>
On 11/06/2014 10:48 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [141106 08:44]:
>> On 11/06/2014 10:37 AM, Tom Rini wrote:
>>
>>>>> device_type = "memory"; + reg = <0x80000000 0x40000000>; /* 1GB
>>>>> to start. Target 2GB */
>>>>
>>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up.
>>>
>>> Yes, it should either be the full and correct value or 0x0 (like a
>>> number of PowerPC platforms do) so it's clear something else gives us
>>> the right value here.
>>
>> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i
>> will repost with proper 2GB. it is better that way in case being used
>> with "other bootloaders" which are not exactly too good like u-boot.
>
> Can you also describe why all the always-on regulators are needed?
yep - will do that similar to
https://patchwork.kernel.org/patch/5125431/ - same rationale unless
there is any specific voltage rail that you are explicitly interested
in that needs additional explanation. Is there additional rails of
interest?
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: Add am57xx-beagle-x15
Date: Thu, 6 Nov 2014 10:53:19 -0600 [thread overview]
Message-ID: <545BA77F.2080609@ti.com> (raw)
In-Reply-To: <20141106164843.GY31454@atomide.com>
On 11/06/2014 10:48 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [141106 08:44]:
>> On 11/06/2014 10:37 AM, Tom Rini wrote:
>>
>>>>> device_type = "memory"; + reg = <0x80000000 0x40000000>; /* 1GB
>>>>> to start. Target 2GB */
>>>>
>>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up.
>>>
>>> Yes, it should either be the full and correct value or 0x0 (like a
>>> number of PowerPC platforms do) so it's clear something else gives us
>>> the right value here.
>>
>> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i
>> will repost with proper 2GB. it is better that way in case being used
>> with "other bootloaders" which are not exactly too good like u-boot.
>
> Can you also describe why all the always-on regulators are needed?
yep - will do that similar to
https://patchwork.kernel.org/patch/5125431/ - same rationale unless
there is any specific voltage rail that you are explicitly interested
in that needs additional explanation. Is there additional rails of
interest?
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tom Rini <trini@ti.com>, <balbi@ti.com>,
<devicetree@vger.kernel.org>, <beagleboard@googlegroups.com>,
<linux-kernel@vger.kernel.org>, <gerald@granddesignsgroup.com>,
<fcooper@ti.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: Add am57xx-beagle-x15
Date: Thu, 6 Nov 2014 10:53:19 -0600 [thread overview]
Message-ID: <545BA77F.2080609@ti.com> (raw)
In-Reply-To: <20141106164843.GY31454@atomide.com>
On 11/06/2014 10:48 AM, Tony Lindgren wrote:
> * Nishanth Menon <nm@ti.com> [141106 08:44]:
>> On 11/06/2014 10:37 AM, Tom Rini wrote:
>>
>>>>> device_type = "memory"; + reg = <0x80000000 0x40000000>; /* 1GB
>>>>> to start. Target 2GB */
>>>>
>>>> 1GiB ? Why would you put this here btw ? u-boot fills this one up.
>>>
>>> Yes, it should either be the full and correct value or 0x0 (like a
>>> number of PowerPC platforms do) so it's clear something else gives us
>>> the right value here.
>>
>> Honest mistake, my bad.. I thought I cleaned up the patch! Sigh!!! i
>> will repost with proper 2GB. it is better that way in case being used
>> with "other bootloaders" which are not exactly too good like u-boot.
>
> Can you also describe why all the always-on regulators are needed?
yep - will do that similar to
https://patchwork.kernel.org/patch/5125431/ - same rationale unless
there is any specific voltage rail that you are explicitly interested
in that needs additional explanation. Is there additional rails of
interest?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2014-11-06 16:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 16:18 [PATCH] ARM: dts: Add am57xx-beagle-x15 Nishanth Menon
2014-11-06 16:18 ` Nishanth Menon
2014-11-06 16:18 ` Nishanth Menon
[not found] ` <1415290702-11353-1-git-send-email-nm-l0cyMroinI0@public.gmane.org>
2014-11-06 16:32 ` Felipe Balbi
2014-11-06 16:32 ` Felipe Balbi
2014-11-06 16:32 ` Felipe Balbi
2014-11-06 16:37 ` Tom Rini
2014-11-06 16:37 ` Tom Rini
2014-11-06 16:37 ` Tom Rini
2014-11-06 16:42 ` Nishanth Menon
2014-11-06 16:42 ` Nishanth Menon
2014-11-06 16:42 ` Nishanth Menon
[not found] ` <545BA513.2090907-l0cyMroinI0@public.gmane.org>
2014-11-06 16:48 ` Tony Lindgren
2014-11-06 16:48 ` Tony Lindgren
2014-11-06 16:48 ` Tony Lindgren
2014-11-06 16:51 ` Gerald Coley
2014-11-06 16:51 ` Gerald Coley
2014-11-06 16:51 ` Gerald Coley
2014-11-06 16:53 ` Nishanth Menon [this message]
2014-11-06 16:53 ` Nishanth Menon
2014-11-06 16:53 ` Nishanth Menon
2014-11-06 17:00 ` Nishanth Menon
2014-11-06 17:00 ` Nishanth Menon
2014-11-06 17:00 ` Nishanth Menon
2014-11-06 16:41 ` Lennart Sorensen
2014-11-06 16:41 ` Lennart Sorensen
2014-11-06 16:44 ` Gerald Coley
2014-11-06 16:44 ` Gerald Coley
2014-11-06 16:44 ` Gerald Coley
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=545BA77F.2080609@ti.com \
--to=nm@ti.com \
--cc=balbi@ti.com \
--cc=beagleboard@googlegroups.com \
--cc=devicetree@vger.kernel.org \
--cc=fcooper@ti.com \
--cc=gerald@granddesignsgroup.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=trini@ti.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 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.