linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Andy Gross <andy.gross@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	David Brown <david.brown@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	linux-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/8] arm64: dts: db820c: add basic board support
Date: Wed, 22 Jun 2016 09:52:12 +0100	[thread overview]
Message-ID: <576A51BC.5090108@linaro.org> (raw)
In-Reply-To: <20160622044916.GF1256@tuxbot>



On 22/06/16 05:49, Bjorn Andersson wrote:
> On Tue 21 Jun 10:22 PDT 2016, Srinivas Kandagatla wrote:
>
> [..]
>> diff --git a/arch/arm64/boot/dts/qcom/apq8096-db820c.dts b/arch/arm64/boot/dts/qcom/apq8096-db820c.dts
> [..]
>> +
>> +/ {
>> +	model = "Qualcomm Technologies, Inc. DB820c";
>> +	compatible = "qcom,apq8096-sbc";
>
> I'm still not buying the concept of this being the one and only
> single-board-computer.
>
+1

AFAIK, The problem is the dtbTool. dtbTool has predefined all the 
platform names along with its platform ID's [1] for auto generating 
board-id, pmic-id and soc-id. dtbTool checks the compatible strings 
along with soc name with its static list, it would fail if it did not 
find a matching combination of soc,platform compatible.

Either we have to cope up with this and have a compatbile strings which 
keep dtbTool happy
  or
Keep patching dtbtool to be more flexible.

There is another problem with dtbTool, We can not use dtbTool with new 
boards from other vendors with own board names, like SD600 or IFC6410 
and so..


IMO, we should patch dtbTool to make it more flexible to cope up with 
situations like this.

> If this compatible fully and exclusively identifies this particular
> board then dtbTool should be updated to follow the product name
> "qcom,apq8096-db820c". If on the other hand this identifies a class of
> single-board-computers, then the compatible should list both
> "qcom,apq8096-dtb820c" and "qcom,apq8096-sbc".

Am not sure this would actually work when we have two boards with same 
sbc platform ID. Which one would the bootloader pick? and on what basis?

>
>
>
> Further more, the ePAPR defines this property as:
> "Specifies a list of platform architectures with which this platform is
> compatible. This property can be used by operating systems in selecting
> platform specific code."
>
> So I think we should follow the common pattern of having the least
> significant entry being "qcom,apq8096".
I agree.

Thanks,
srini

[1] https://source.codeaurora.org/quic/kernel/skales/tree/dtbTool#n83



>
>> +};
>
> Regards,
> Bjorn
>

  reply	other threads:[~2016-06-22  8:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 17:22 [PATCH v2 0/8] arm64: dts: db820c: Add basic board support Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 1/8] arm64: dts: db820c: add " Srinivas Kandagatla
2016-06-22  4:49   ` Bjorn Andersson
2016-06-22  8:52     ` Srinivas Kandagatla [this message]
     [not found]       ` <576A51BC.5090108-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-06-22 16:04         ` Bjorn Andersson
2016-06-22 13:06   ` Mark Rutland
2016-06-21 17:22 ` [PATCH v2 2/8] arm64: dts: db820c: add support to LS-UART0 Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 3/8] arm64: dts: db820c: add support to LS-I2C0 Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 4/8] arm64: dts: db820c: add support to LS-I2C1 Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 5/8] arm64: dts: db820c: add support to I2C on HS Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 6/8] arm64: dts: db820c: add support to LS-SPI0 Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 7/8] arm64: dts: db820c: add support to SPI on HS Srinivas Kandagatla
2016-06-21 17:22 ` [PATCH v2 8/8] arm64: dts: db820c: add support to external sd card Srinivas Kandagatla

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=576A51BC.5090108@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).