From: Vikash Garodia <quic_vgarodia@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] dt-bindings: media: qcom,sm8550-iris: update power domain name
Date: Wed, 12 Mar 2025 18:25:48 +0530 [thread overview]
Message-ID: <c6e601d1-28ff-2a24-0b98-e79006bd7a8e@quicinc.com> (raw)
In-Reply-To: <85bd865b-71e7-40e1-9303-e970d338cb59@kernel.org>
On 3/12/2025 2:14 PM, Krzysztof Kozlowski wrote:
> On 11/03/2025 18:47, Vikash Garodia wrote:
>>
>> On 3/11/2025 11:03 PM, Krzysztof Kozlowski wrote:
>>> On 11/03/2025 13:03, Vikash Garodia wrote:
>>>> Not all platforms has a collapsible mx, so use the more generic naming
>>>> of mx in the binding.
>>>>
>>>
>>> No, neither tested, nor justified. Read the file. How many platforms do
>>> you have there? One. Out of this one platform you claim not all of them
>>> have MX collapsible, so you want MX?
>> Let say we have one which is non-collapsible, what should be the way in that
>> case to use the bindings which differ only in the MX/MXC part ?
>
>
> I don't care about imaginary things. Send patches for real hardware. How
> does collapsibility of the domain change the real hardware interface?
It does not. I am now thinking to drop this patch altogether, and continue to
use MXC as defined in bindings, irrespective of connection to hardware as MX or
MXC. For ex SM8550/SA8775P have MXC, while QCS8300 have MX, but again, as you
mentioned, these difference just alters some property in DT, binding can remain
same.
Regards,
Vikash
next prev parent reply other threads:[~2025-03-12 12:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 12:03 [PATCH 0/4] media: qcom: iris: add support for SA8775P Vikash Garodia
2025-03-11 12:03 ` [PATCH 1/4] dt-bindings: media: qcom,sm8550-iris: update power domain name Vikash Garodia
2025-03-11 14:52 ` Rob Herring (Arm)
2025-03-11 15:07 ` Dmitry Baryshkov
2025-03-11 15:11 ` Vikash Garodia
2025-03-11 15:35 ` Dmitry Baryshkov
2025-03-11 19:19 ` Vikash Garodia
2025-03-11 22:13 ` Dmitry Baryshkov
2025-03-11 16:24 ` Konrad Dybcio
2025-03-11 17:33 ` Krzysztof Kozlowski
2025-03-11 17:47 ` Vikash Garodia
2025-03-12 8:44 ` Krzysztof Kozlowski
2025-03-12 12:55 ` Vikash Garodia [this message]
2025-03-11 12:03 ` [PATCH 2/4] dt-bindings: media: qcom,sm8550-iris: document SA8775p IRIS accelerator Vikash Garodia
2025-03-11 15:31 ` Dmitry Baryshkov
2025-03-12 8:07 ` Vikash Garodia
2025-03-12 8:51 ` Dmitry Baryshkov
2025-03-11 17:35 ` Krzysztof Kozlowski
2025-03-11 17:57 ` Vikash Garodia
2025-03-12 8:42 ` Krzysztof Kozlowski
2025-03-11 12:03 ` [PATCH 3/4] arm64: dts: qcom: sa8775p: add support for video node Vikash Garodia
2025-03-15 13:43 ` Konrad Dybcio
2025-03-15 14:04 ` Konrad Dybcio
2025-03-15 18:32 ` Dmitry Baryshkov
2025-03-17 6:00 ` Vikash Garodia
2025-03-17 11:29 ` Dmitry Baryshkov
2025-03-18 14:24 ` Vikash Garodia
2025-03-18 14:33 ` Konrad Dybcio
2025-03-18 15:38 ` Vikash Garodia
2025-03-17 11:31 ` Dmitry Baryshkov
2025-03-18 12:22 ` Konrad Dybcio
2025-03-18 13:43 ` Vikash Garodia
2025-03-11 12:03 ` [PATCH 4/4] media: iris: add compatible string for sa8775p Vikash Garodia
2025-03-11 15:32 ` Dmitry Baryshkov
2025-03-11 17:34 ` 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=c6e601d1-28ff-2a24-0b98-e79006bd7a8e@quicinc.com \
--to=quic_vgarodia@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_dikshita@quicinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox