linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Doug Anderson <dianders@chromium.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Joseph S. Barrera III" <joebar@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Alexandru M Stan <amstan@chromium.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 3/5] arm64: dts: qcom: sc7180: Add quackingstick dts files
Date: Tue, 3 May 2022 17:55:18 +0200	[thread overview]
Message-ID: <e321d8c2-950c-a194-04a3-1fe2659749e9@linaro.org> (raw)
In-Reply-To: <CAD=FV=WhAqQnxwNaW4kfq9Wuwsz6YYzBgSn=KX9Se_5o2mkcsA@mail.gmail.com>

On 03/05/2022 17:34, Doug Anderson wrote:
> Hi,
> 
> On Tue, May 3, 2022 at 8:31 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 30/04/2022 10:15, Joseph S. Barrera III wrote:
>>> Quackingstick is a trogdor-based board. These dts files are copies from
>>> the downstream Chrome OS 5.4 kernel, but with downstream bits removed.
>>>
>>> Signed-off-by: Joseph S. Barrera III <joebar@chromium.org>
>>
>> (...)
>>
>>> +/*
>>> + * Google Quackingstick board device tree source
>>> + *
>>> + * Copyright 2021 Google LLC.
>>> + *
>>> + * SKU: 0x601 => 1537
>>> + *  - bits 11..8: Panel ID: 0x6 (AUO)
>>> + */
>>> +
>>> +#include "sc7180-trogdor-quackingstick.dtsi"
>>> +
>>> +/ {
>>> +     model = "Google Quackingstick (rev0+)";
>>> +     compatible = "google,quackingstick-sku1537", "qcom,sc7180";
>>
>> Here and in other patches you keep adding undocumented board compatibles.
> 
> Sure, but perhaps we could continue the conversation at:
> 
> https://lore.kernel.org/r/CAD=FV=W_SA-3PfDFi-Gkjk9pew5bchFNjQhXX8MkZyuy5UohEQ@mail.gmail.com/
> 
> ...to avoid forking it and losing all the context.

It's not that close to that discussion because none of compatibles here
are documented and we discussed about documenting specific revisions.


Best regards,
Krzysztof

  reply	other threads:[~2022-05-03 15:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  8:15 [PATCH 1/5] arm64: dts: qcom: sc7180: Add wormdingler dts files Joseph S. Barrera III
2022-04-30  8:15 ` [PATCH 2/5] arm64: dts: qcom: sc7180: Add mrbland " Joseph S. Barrera III
2022-05-02 17:17   ` Doug Anderson
2022-04-30  8:15 ` [PATCH 3/5] arm64: dts: qcom: sc7180: Add quackingstick " Joseph S. Barrera III
2022-05-02 17:17   ` Doug Anderson
2022-05-03 15:31   ` Krzysztof Kozlowski
2022-05-03 15:34     ` Doug Anderson
2022-05-03 15:55       ` Krzysztof Kozlowski [this message]
2022-05-03 16:16         ` Doug Anderson
2022-04-30  8:15 ` [PATCH 4/5] arm64: dts: qcom: sc7180: Add pazquel " Joseph S. Barrera III
2022-05-02 17:17   ` Doug Anderson
2022-04-30  8:15 ` [PATCH 5/5] arm64: dts: qcom: sc7180: Add kingoftown " Joseph S. Barrera III
2022-05-02 17:17   ` Doug Anderson
2022-05-02 17:17 ` [PATCH 1/5] arm64: dts: qcom: sc7180: Add wormdingler " Doug Anderson

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=e321d8c2-950c-a194-04a3-1fe2659749e9@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=amstan@chromium.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=joebar@chromium.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@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).