linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@linaro.org>
To: Rob Clark <robdclark@gmail.com>
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-soc@vger.kernel.org, Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: Rename SBC to DragonBoard 410c
Date: Thu, 5 Oct 2017 15:54:45 +0300	[thread overview]
Message-ID: <CAAqcGH=aZSg7Dzv_Y2erUxmCaN7LXYqxgO9wnPKqSVX1fBuCMg@mail.gmail.com> (raw)
In-Reply-To: <CAF6AEGvtfAYx5mgg9mMVeXdO5mStD9gJvi5+Pp46jYj-e8WnOQ@mail.gmail.com>

On 5 October 2017 at 00:23, Rob Clark <robdclark@gmail.com> wrote:
> On Tue, Oct 3, 2017 at 2:54 PM, Rob Clark <robdclark@gmail.com> wrote:
>> On Tue, Oct 3, 2017 at 1:49 PM, Nicolas Dechesne
>> <nicolas.dechesne@linaro.org> wrote:
>>> On Tue, Oct 3, 2017 at 6:37 PM, Rob Clark <robdclark@gmail.com> wrote:
>>>> On Tue, Oct 3, 2017 at 8:25 AM, Srinivas Kandagatla
>>>> <srinivas.kandagatla@linaro.org> wrote:
>>>>>
>>>>>
>>>>> On 03/10/17 10:11, Linus Walleij wrote:
>>>>>>
>>>>>> Naming the DragonBoard 410c "SBC" (I guess "single board computer")
>>>>>> is not very helpful for users looking for their device tree in
>>>>>> the kernel. Also the db820c is named properly.
>>>>>>
>>>>>> Rectify this, simply, do not change the compatible strings but name
>>>>>> the DTS files in a consistent manner.
>>>>>>
>>>>>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
>>>>>
>>>>> I did not like the sbc naming convention too, This was primarily done due to
>>>>> some legacy build tools + bootloaders which have used sbc compatible to
>>>>> identify boards from multiple dtb blobs. Now that we can append dtb to
>>>>> kernel with new LK, this should not be a issue anymore.
>>>>
>>>> maybe it would be an idea to update skales/dbttool first to look for
>>>> the new name, and then give people some time to upgrade, before
>>>> changing this in the kernel.  Otherwise I expect you'll cause some
>>>> confusion..
>>>
>>> iirc, skale is using the compatible name, not the filename.
>>>
>>
>> ahh, yes, I think you are right.. u-boot is using a different filename.
>>
>> So in this case, no issue to pick a saner name :-)
>>
>
> So, actually u-boot encodes the board's fdtname..  so as much as I'd
> like to rename it to something more sane, unless the kernel can manage
> to install a symlink for backwards compat, NAK

In some cases the partition where dtbs is FAT, which doesn't do
symlinks. There are various instructions around that refer to editing
apq8016-sbc.dts already[1]. The goal of the patch is to reduce
confusion, but requiring different firmware depending on kernel
version, and/or updated userspace, is actually going to increase the
confusion and frustration. So I have echo Rob here.

> I was trying to think of hacks for u-boot to check for multiple fdt
> names, but if we want to get to the point of being able to install
> multiple distro's on a single disk, we actually need to pass fdtname
> to grub (where distro specific grub.cfg is encoding the UUID of the
> distro's /boot partition, so it knows where to load the dtb from)..
> this gets nearly impossible when one name becomes multiple names.  So
> hurray for the fdt name becoming accidental ABI!

It's unfortunate yes.

But is renaming .dts really needed to make finding the right DTS easier?

Maybe just pick this part the patch:

-       model = "Qualcomm Technologies, Inc. APQ 8016 SBC";
+       model = "Qualcomm Technologies, Inc. APQ 8016 DragonBoard 410c";

then you can "git grep 410c " to find the file. This is how find the
Nexus, Pixel and Jetson TX dts for example.

[1] https://www.google.fi/search?q=instructions+apq8016-sbc

Riku

  parent reply	other threads:[~2017-10-05 12:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  9:11 [PATCH 1/2] arm64: qcom: sbc: Name GPIO lines Linus Walleij
2017-10-03  9:11 ` [PATCH 2/2] arm64: dts: qcom: Rename SBC to DragonBoard 410c Linus Walleij
2017-10-03 12:25   ` Srinivas Kandagatla
2017-10-03 16:37     ` Rob Clark
2017-10-03 17:49       ` Nicolas Dechesne
2017-10-03 18:54         ` Rob Clark
2017-10-04 21:23           ` Rob Clark
2017-10-04 22:09             ` Stephen Boyd
2017-10-04 22:12               ` Rob Clark
2017-10-04 23:21                 ` Stephen Boyd
2017-10-04 23:49                   ` Rob Clark
2017-10-05 12:54             ` Riku Voipio [this message]
2017-10-05 13:06               ` Alexander Graf
2017-10-06  4:41                 ` Andy Gross
2017-10-03 20:58   ` Bjorn Andersson
2017-10-04 21:45 ` [PATCH 1/2] arm64: qcom: sbc: Name GPIO lines Stephen Boyd

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='CAAqcGH=aZSg7Dzv_Y2erUxmCaN7LXYqxgO9wnPKqSVX1fBuCMg@mail.gmail.com' \
    --to=riku.voipio@linaro.org \
    --cc=agraf@suse.de \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=robdclark@gmail.com \
    --cc=sboyd@codeaurora.org \
    --cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).