All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	Casey Connolly <casey.connolly@linaro.org>,
	Joel Selvaraj <joelselvaraj.oss@gmail.com>,
	Jens Reidel <adrian@travitia.xyz>,
	Petr Hodina <petr.hodina@protonmail.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sdm845-xiaomi-beryllium: Fix compatible strings
Date: Sun, 5 Apr 2026 10:09:18 +0200	[thread overview]
Message-ID: <61a52b49-4765-41c5-b186-eafeb0b0b244@ixit.cz> (raw)
In-Reply-To: <20260405-tidy-dancing-albatross-1b1cf4@quoll>

On 05/04/2026 10:02, Krzysztof Kozlowski wrote:
> On Fri, Apr 03, 2026 at 06:55:34PM +0200, David Heidelberg wrote:
>> From: Jens Reidel <adrian@travitia.xyz>
>>
>> The most specific strings should come first (panel variant included),
>> then the more generic ones (device and SoC).
>>
>> This is necessary for hexagonrpcd to guess the HexagonFS path for the
>> device. It tries all of the compatible entries, but if none for
>> xiaomi,beryllium existed it wouldn't be able to guess it.
>>
>> Fixes: bcf429831ecb ("arm64: dts: qcom: sdm845-xiaomi-beryllium-ebbg: introduce Xiaomi Poco F1 EBBG variant")
>> Fixes: dd6459a0890a ("arm64: dts: qcom: split beryllium dts into common dtsi and tianma dts")
>> Signed-off-by: Jens Reidel <adrian@travitia.xyz>
>> Signed-off-by: David Heidelberg <david@ixit.cz>
>> ---
>>   arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-ebbg.dts   | 2 +-
>>   arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-tianma.dts | 2 +-
>>   2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-ebbg.dts b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-ebbg.dts
>> index 2d6f0e382a6cb..d157622f84d13 100644
>> --- a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-ebbg.dts
>> +++ b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-ebbg.dts
>> @@ -6,7 +6,7 @@
>>   
>>   / {
>>   	model = "Xiaomi Pocophone F1 (EBBG)";
>> -	compatible = "xiaomi,beryllium-ebbg", "qcom,sdm845";
>> +	compatible = "xiaomi,beryllium-ebbg", "xiaomi,beryllium", "qcom,sdm845";
> 
> So now for all users of this ABI, the ebbg variant will be treated like
> it was Tianma. Your commit msg should try to explain the impact of this,
> beside the hexagonrpcd.

Sure, I'll update the commit msg.

> 
> Technically this is ABI change.
> 
> Best regards,
> Krzysztof
> 

-- 
David Heidelberg


      reply	other threads:[~2026-04-05  8:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 16:55 [PATCH 0/2] Correct Xiaomi Poco F1 compatible strings and evaluation David Heidelberg
2026-04-03 16:55 ` David Heidelberg via B4 Relay
2026-04-03 16:55 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Xiaomi Poco F1 Tianma variant bindings David Heidelberg
2026-04-03 16:55   ` David Heidelberg via B4 Relay
2026-04-05  7:55   ` Krzysztof Kozlowski
2026-04-05  8:01     ` David Heidelberg
2026-04-05  8:55       ` Krzysztof Kozlowski
2026-04-05  9:19         ` David Heidelberg
2026-04-03 16:55 ` [PATCH 2/2] arm64: dts: qcom: sdm845-xiaomi-beryllium: Fix compatible strings David Heidelberg
2026-04-03 16:55   ` David Heidelberg via B4 Relay
2026-04-05  8:02   ` Krzysztof Kozlowski
2026-04-05  8:09     ` David Heidelberg [this message]

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=61a52b49-4765-41c5-b186-eafeb0b0b244@ixit.cz \
    --to=david@ixit.cz \
    --cc=adrian@travitia.xyz \
    --cc=andersson@kernel.org \
    --cc=casey.connolly@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joelselvaraj.oss@gmail.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=petr.hodina@protonmail.com \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.