mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kathiravan T <quic_kathirav@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Andy Gross <agross@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Cc: <quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
	<quic_anusha@quicinc.com>, <quic_saahtoma@quicinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom,ids: drop the IPQ5019 SoC ID
Date: Tue, 11 Jul 2023 16:32:41 +0530	[thread overview]
Message-ID: <a3262be5-be66-661c-1feb-d663a057c2b2@quicinc.com> (raw)
In-Reply-To: <55e55042-5189-15cb-5b0f-4c7f321a4f61@linaro.org>


On 7/10/2023 5:40 PM, Konrad Dybcio wrote:
> On 10.07.2023 13:37, Krzysztof Kozlowski wrote:
>> On 10/07/2023 12:54, Kathiravan T wrote:
>>> IPQ5019 SoC is not available in production. Lets drop it.
>>>
>>> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
>>> ---
>>>   include/dt-bindings/arm/qcom,ids.h | 1 -
>>>   1 file changed, 1 deletion(-)
>>>
>>> diff --git a/include/dt-bindings/arm/qcom,ids.h b/include/dt-bindings/arm/qcom,ids.h
>>> index bcbe9ee2cdaf..179dd56b2d95 100644
>>> --- a/include/dt-bindings/arm/qcom,ids.h
>>> +++ b/include/dt-bindings/arm/qcom,ids.h
>>> @@ -250,7 +250,6 @@
>>>   #define QCOM_ID_QRU1000			539
>>>   #define QCOM_ID_QDU1000			545
>>>   #define QCOM_ID_QDU1010			587
>>> -#define QCOM_ID_IPQ5019			569
>> What about users of this binding? What's the impact on them? When did
>> the SoC become obsolete and unsupported by Qualcomm? Remember that
>> ceasing a production does not mean that magically all users of a product
>> disappear...
> This + from my experience, SOCID entries are set in stone and freed
> indices are never reclaimed


This SKU is planned but never productized. That's why I removed it.

May be I should be more precise in the commit title. Should I leave it 
as it is / remove it?


Thanks, Kathiravan T.

>
> Konrad
>>
>> Best regards,
>> Krzysztof
>>

  reply	other threads:[~2023-07-11 11:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 10:54 [PATCH 0/2] Drop " Kathiravan T
2023-07-10 10:54 ` [PATCH 1/2] dt-bindings: arm: qcom,ids: drop " Kathiravan T
2023-07-10 11:37   ` Krzysztof Kozlowski
2023-07-10 12:10     ` Konrad Dybcio
2023-07-11 11:02       ` Kathiravan T [this message]
2023-07-11 11:11         ` Krzysztof Kozlowski
2023-07-10 10:54 ` [PATCH 2/2] soc: qcom: socinfo: " Kathiravan T
2023-07-10 11:38   ` Krzysztof Kozlowski

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=a3262be5-be66-661c-1feb-d663a057c2b2@quicinc.com \
    --to=quic_kathirav@quicinc.com \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=quic_anusha@quicinc.com \
    --cc=quic_saahtoma@quicinc.com \
    --cc=quic_sjaganat@quicinc.com \
    --cc=quic_srichara@quicinc.com \
    --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

all inboxes | Powered by JetHome®