From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: <balbi@ti.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 Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm: boot: dts: build keystone devicetree blob
Date: Tue, 25 Mar 2014 09:21:07 -0400 [thread overview]
Message-ID: <533182C3.9060708@ti.com> (raw)
In-Reply-To: <20140321144328.GC12310@saruman.home>
On Friday 21 March 2014 10:43 AM, Felipe Balbi wrote:
> On Fri, Mar 21, 2014 at 10:40:00AM -0400, Santosh Shilimkar wrote:
>> On Wednesday 12 March 2014 12:35 PM, Santosh Shilimkar wrote:
>>> On Wednesday 12 March 2014 11:48 PM, Felipe Balbi wrote:
>>>> Currently, even when building keystone only
>>>> kernel builds, DTB won't get build because
>>>> we lack a Makefile rule to get it compiled.
>>>>
>>>> This patch adds that rule so mainline kernel
>>>> users have a chance to use up-to-date DTB on
>>>> keystone 2 platforms.
>>>>
>>>> Signed-off-by: Felipe Balbi <balbi@ti.com>
>>>> ---
>>>>
>>> We have been building dtbs with explicit command
>>> instead of dtbs since it was just one dtb so far
>>> supported. Was planning to add the rule once more
>>> boards get added. Now with Lamarr and Edision in
>>> for next merge window, will do that post 3.15-rc1.
>>>
>> Just to close the loop, I added a patch as part
>> of my 3.15 fixes which builds all keystone dt
>> blobs.
>
> cool, thanks
>
Here is the updated patch which I commited to fixes branch.
Sorry to miss your reported-by tag. I just missed it.
>From 400550ae7e778302a45d2952ac75907903e2610c Mon Sep 17 00:00:00 2001
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
Date: Tue, 18 Mar 2014 16:02:34 -0400
Subject: [PATCH] ARM: dts: Build all keystone dt blobs
Now we have additional two SOC/boards supported, so add
make file rule so that all device tree blobs can be build
for keystone with 'make dtbs'.
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
arch/arm/boot/dts/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index b9d6a8b..49ff796 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -81,6 +81,9 @@ dtb-$(CONFIG_ARCH_HIGHBANK) += highbank.dtb \
ecx-2000.dtb
dtb-$(CONFIG_ARCH_INTEGRATOR) += integratorap.dtb \
integratorcp.dtb
+dtb-$(CONFIG_ARCH_KEYSTONE) += k2hk-evm.dtb \
+ k2l-evm.dtb \
+ k2e-evm.dtb
dtb-$(CONFIG_ARCH_LPC32XX) += ea3250.dtb phy3250.dtb
dtb-$(CONFIG_ARCH_KIRKWOOD) += kirkwood-cloudbox.dtb \
kirkwood-db-88f6281.dtb \
--
1.7.9.5
prev parent reply other threads:[~2014-03-25 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 15:48 [PATCH] arm: boot: dts: build keystone devicetree blob Felipe Balbi
2014-03-12 16:35 ` Santosh Shilimkar
2014-03-12 16:53 ` Felipe Balbi
2014-03-21 14:40 ` Santosh Shilimkar
2014-03-21 14:43 ` Felipe Balbi
2014-03-25 13:21 ` Santosh Shilimkar [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=533182C3.9060708@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=balbi@ti.com \
--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@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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