devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list@gmail.com>
To: Tero Kristo <t-kristo@ti.com>,
	catalin.marinas@arm.com, will.deacon@arm.com,
	linux@armlinux.org.uk, robh+dt@kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/7] ARM32/64: DT overlay build support
Date: Thu, 30 Aug 2018 13:32:28 -0700	[thread overview]
Message-ID: <a137359f-f836-c8eb-61b4-9d1d4907ad93@gmail.com> (raw)
In-Reply-To: <183d979a-3849-7199-417f-3572b00dca5b@ti.com>

Hi Tero,

(Really adding Mark as a cc: this time.  Last time I added him as
a bcc: by mistake.)


On 08/30/18 10:12, Tero Kristo wrote:
> On 29/08/18 21:40, Frank Rowand wrote:
>> + Mark Rutland, just in case he is interested
>>
>> On 08/28/18 05:32, Tero Kristo wrote:
>>> Hi,
>>>
>>> This series introduces devicetree overlay building support for ARM
>>> platforms. The .dtbo target is introduced globally, then makefile
>>> changes for both arm32/64 for supporting the .dtbo target, changes
>>> to support sub-dir makefile flags, and finally adding the DTC flags
>>> override for TI platforms, as that is where we want to introduce
>>> the DT overlay support initially.
>>>
>>> The ARM makefile changes for supporting DTS sub-makefiles don't look
>>> too clean, but that was the only way I could figure out how to
>>> get it done.
>>>
>>> -Tero
>>>
>>> -- 
>>>
>>
>> This series does three unrelated things:
> 
> Well, I was kind of trying to show the whole solution here but...

That actually makes sense, and normally I wouldn't have asked for the
split.  It might be the case that I am being too cautious, and maybe
there won't be much discussion at all.  I was just concerned that in
this case some of the concepts might get overlooked due to discussion
of other concepts.  I'm also expecting different people to care
about each of the concepts.

> 
>> (1) create a ti specific dts subdirectory arch/arm/boot/dts/ti/
>>
>> (2) create a rule for creating a .dtbo from a .dtso
>>
>> (3) add a dtc compile flag to add phandle symbol information to
>>      all .dtb files created from arch/arm/boot/dts/ti/ and
>>      arch/arm64/boot/dts/ti/
>>
>> Please split the patches into three independent series so that
>> each of the three concepts can be discussed separately. 
> 
> Ok will do that, hopefully tomorrow. Didn't manage to squeeze in time to do it today.

Thanks, I appreciate your flexibility.

-Frank

> 
> -Tero
> -- 
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
> 


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-08-30 20:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 12:32 [PATCH 0/7] ARM32/64: DT overlay build support Tero Kristo
2018-08-28 12:32 ` [PATCH 1/7] kbuild: add support for building %.dtbo targets Tero Kristo
2018-08-28 12:32 ` [PATCH 2/7] ARM: dts: add support for building DT overlays Tero Kristo
2018-08-28 12:32 ` [PATCH 3/7] ARM: dts: add support for individual build flags for DT subdirs Tero Kristo
2018-08-28 12:32 ` [PATCH 4/7] arm64: dts: add support for building DT overlays Tero Kristo
2018-08-28 12:32 ` [PATCH 5/7] arm64: dts: add support for per sub-dir makefiles for DT building Tero Kristo
2018-08-28 12:32 ` [PATCH 6/7] ARM: dts: ti: add support for building Texas Instruments specific overlays Tero Kristo
2018-08-28 12:32 ` [PATCH 7/7] arm64: ti: add support for building Texas instruments overlays Tero Kristo
2018-08-29 18:40 ` [PATCH 0/7] ARM32/64: DT overlay build support Frank Rowand
2018-08-30 17:12   ` Tero Kristo
2018-08-30 20:32     ` Frank Rowand [this message]
2018-09-03  9:03       ` Tero Kristo
2018-09-03 17:26         ` Frank Rowand

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=a137359f-f836-c8eb-61b4-9d1d4907ad93@gmail.com \
    --to=frowand.list@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=t-kristo@ti.com \
    --cc=will.deacon@arm.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).