public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] dm: dts: ls2085a: Bring in ls2085a dts files from linux kernel
Date: Tue, 14 Jul 2015 16:16:42 -0700	[thread overview]
Message-ID: <55A5985A.2070507@freescale.com> (raw)
In-Reply-To: <20150713092826.GB19083@leverpostej>



On 07/13/2015 02:28 AM, Mark Rutland wrote:
> On Wed, Jul 08, 2015 at 08:31:47AM +0100, Sharma Bhupesh wrote:
>>> -----Original Message-----
>>> From: U-Boot [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Wang
>>> Haikun
>>> On 7/8/2015 3:13 PM, Bin Meng wrote:
>>>> Hi,
>>>>
>>>> On Wed, Jul 8, 2015 at 2:51 PM, Wang Haikun <Haikun.Wang@freescale.com>
>>> wrote:
>>>>> On 6/26/2015 7:53 PM, Haikun Wang wrote:
>>>>>> From: Haikun Wang <Haikun.Wang@freescale.com>
>>>>>>
>>>>>> Bring in required device tree files for ls2085a from Linux.
>>>>>> These are initially unchanged and have a number of pieces not needed
>>> by U-Boot.
>>>>> Hi Simon,
>>>>>
>>>>> I got below comment when review this patch internal.
>>>>> Please help me confirm.
>>>>>
>>>>> "For new platforms like ARM64, it was discussed to not duplicate the
>>>>> DTS in u-boot and Linux, simply because that will break compatibility
>>>>> with other bootloaders like Linaro's BootMonitor and UEFI bootloader,
>>>>> which do not place the DTS in the bootloader. Also in near future,
>>>>> with DTS being replaced by ACPI gradually for ARM64 platforms, it was
>>>>> discussed that in a longer run it would be beneficial to move DTS out
>>>>> of both u-boot and Linux and maintain it as a separate tree."
>>>>>
>>>>
>>>> I think UEFI + ACPI is only required for ARMv8 servers, not for all
>>>> ARMv8 processors. Is ls2085a a processor targeting the server market?
>>> No, at least it's not our major market.
>>> I want to know whether we have made a conclusion that u-boot will not add
>>> Arm64 dts files?
>>
>> Adding Russell and Mark for their thoughts.
>>
>> AFAIK there were discussions to generate common DTS files for PPC and ARM platforms,
>> where it was discussed that in a longer run it would be beneficial to move DTS out
>> of both u-boot and Linux and maintain it as a separate tree.
> 
> While I would like to see dts moved out of the kernel, I don't see this
> happening in the short term.
> 
> I'm not sure what the best strategy is w.r.t. U-Boot and dts.
> 

Looks like we agree to put this dts in u-boot, at least temporarily. I am
preparing to bring it in to enable SPI devices.

York

  reply	other threads:[~2015-07-14 23:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 11:48 [U-Boot] [PATCH 1/3] dm: dts: ls2085a: Bring in ls2085a dts files from linux kernel Haikun Wang
2015-07-08  6:51 ` Wang Haikun
2015-07-08  7:13   ` Bin Meng
2015-07-08  7:27     ` Wang Haikun
2015-07-08  7:31       ` Sharma Bhupesh
2015-07-08  9:19         ` Albert ARIBAUD
2015-07-08 10:31           ` Sharma Bhupesh
2015-07-08 14:04             ` Albert ARIBAUD
2015-07-13  9:28         ` Mark Rutland
2015-07-14 23:16           ` York Sun [this message]
2015-07-20 21:17 ` York Sun

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=55A5985A.2070507@freescale.com \
    --to=yorksun@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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