Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: <forbidden405@foxmail.com>
To: "'Krzysztof Kozlowski'" <krzysztof.kozlowski@linaro.org>,
	"'Andy Gross'" <agross@kernel.org>,
	"'Bjorn Andersson'" <andersson@kernel.org>,
	"'Konrad Dybcio'" <konrad.dybcio@linaro.org>,
	"'Rob Herring'" <robh+dt@kernel.org>,
	"'Krzysztof Kozlowski'" <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: "'Jaime Breva'" <jbreva@nayarsystems.com>,
	<~postmarketos/upstreaming@lists.sr.ht>,
	"'Nikita Travkin'" <nikita@trvn.ru>
Subject: RE: [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896
Date: Wed, 11 Jan 2023 03:56:23 +0800	[thread overview]
Message-ID: <tencent_2068AC70F1DA5AF46F600C7718FEB1B98307@qq.com> (raw)
In-Reply-To: <0453b098-91db-1918-38ae-a7db0408460c@linaro.org>

On 10/01/2023 20:32, krzysztof.kozlowski@linaro.org wrote:
> 
> Then I am not sure if we want to support such devices mainline. It is not
only
> anonymity but simply not following standards and practices.
> What's more there is no guarantee what this device is. If there is no
known
> manufacturer, anytime another device from anyone can claim it is also
uf896.
> IOW, what guarantees you have that other person who has something looking
> like "uf896" actually has something the same as you and can use your DTB?

There is a label printed (i.e. ufi001c or uf896 or something else but not
getting mainlined now) on the board, different models have different
labels(and different board design). And currently I know all ufi001c(even
some other models) shares the same device tree, as a downstream device tree
has been tested by thousands of people. I'm not familiar with uf896 as it is
owned by Nikita Travkin and tested by him. The device sells very well and
many people will benefit from mainlining.


  reply	other threads:[~2023-01-10 19:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230110155014.31664-1-forbidden405@foxmail.com>
2023-01-10 15:50 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add zhihe Yang Xiwen
2023-01-10 16:32   ` Krzysztof Kozlowski
2023-01-10 15:50 ` [PATCH 2/3] dt-bindings: qcom: Ducument bindings for new msm8916-zhihe-uf896 and msm8916-zhihe-ufi001c Yang Xiwen
2023-01-10 16:31   ` Krzysztof Kozlowski
2023-01-10 15:50 ` [PATCH 3/3] arm64: dts: qcom: msm8916-zhihe: Add initial device tree for zhihe Wifi/LTE dongle UFI-001C and uf896 Yang Xiwen
2023-01-10 16:35   ` Krzysztof Kozlowski
2023-01-10 18:17     ` forbidden405
2023-01-10 18:29       ` Krzysztof Kozlowski
2023-01-10 18:58         ` forbidden405
2023-01-10 19:25           ` Krzysztof Kozlowski
2023-01-10 19:56             ` forbidden405 [this message]
2023-01-11  9:06               ` Krzysztof Kozlowski
2023-01-11 10:21                 ` forbidden405
2023-01-19  0:24   ` Bjorn Andersson

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=tencent_2068AC70F1DA5AF46F600C7718FEB1B98307@qq.com \
    --to=forbidden405@foxmail.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jbreva@nayarsystems.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikita@trvn.ru \
    --cc=robh+dt@kernel.org \
    --cc=~postmarketos/upstreaming@lists.sr.ht \
    /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