Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Wenmeng Liu <quic_wenmliu@qualcomm.com>
To: Bryan O'Donoghue <bod@kernel.org>,
	Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
	Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	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-media@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] media: qcom: camss: add support for SM6150 camss
Date: Thu, 16 Oct 2025 20:36:46 +0800	[thread overview]
Message-ID: <e4be125c-752e-46c9-9637-fe23cbf04b1a@qualcomm.com> (raw)
In-Reply-To: <1d4d4627-7fe9-43b2-8622-8ffc078e30a6@kernel.org>



On 10/16/2025 6:29 PM, Bryan O'Donoghue wrote:
> On 16/10/2025 11:22, Wenmeng Liu wrote:
>> The camera subsystem for SM6150 which is based on Spectra 230.
>>
>> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
> 
> Your commit log needs more detail.
> 
> - VFE17x version what ?
> - CSID version .. gen2 so CSID 480 is it ?
> - CSIPHY process node would be nice
> 
> 

Yes, will add more detail in next version.
For SM6150, vfe and csid version is 170(vfe170, csid170),
csiphy version is csiphy-v2.0.

>> ---
>>   .../platform/qcom/camss/camss-csiphy-3ph-1-0.c     |   2 +
>>   drivers/media/platform/qcom/camss/camss-vfe.c      |   2 +
>>   drivers/media/platform/qcom/camss/camss.c          | 186 +++++++++++ 
>> ++++++++++
>>   drivers/media/platform/qcom/camss/camss.h          |   1 +
>>   4 files changed, 191 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/camss/camss-csiphy-3ph-1-0.c 
>> b/drivers/media/platform/qcom/camss/camss-csiphy-3ph-1-0.c
>> index 
>> a229ba04b158739ddfe4076bdd28167a309f13ea..7bc524a9c4bbe3a316e366868e9d636e58d5956a 100644
>> --- a/drivers/media/platform/qcom/camss/camss-csiphy-3ph-1-0.c
>> +++ b/drivers/media/platform/qcom/camss/camss-csiphy-3ph-1-0.c
>> @@ -908,6 +908,7 @@ static bool csiphy_is_gen2(u32 version)
>>       switch (version) {
>>       case CAMSS_2290:
>> +    case CAMSS_6150:
>>       case CAMSS_7280:
>>       case CAMSS_8250:
>>       case CAMSS_8280XP:
>> @@ -996,6 +997,7 @@ static int csiphy_init(struct csiphy_device *csiphy)
>>           regs->lane_array_size = ARRAY_SIZE(lane_regs_sdm845);
>>           break;
>>       case CAMSS_2290:
>> +    case CAMSS_6150:
>>           regs->lane_regs = &lane_regs_qcm2290[0];
> 
> You don't need to specify the array index for that.
> 

Here I have only added "case CAMSS_6150:", then do I need to modify the 
part of "&lane_regs_qcm2290[0]"?

>>           regs->lane_array_size = ARRAY_SIZE(lane_regs_qcm2290);
>>           break;

Best regards,
Wenmeng

B

  reply	other threads:[~2025-10-16 12:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 10:22 [PATCH 0/3] media: qcom: camss: Add sm6150 camss support Wenmeng Liu
2025-10-16 10:22 ` [PATCH 1/3] media: dt-bindings: Add qcom,sm6150-camss Wenmeng Liu
2025-10-16 10:43   ` Bryan O'Donoghue
2025-10-16 13:00     ` Wenmeng Liu
2025-10-16 13:31   ` Vladimir Zapolskiy
2025-10-28  9:49   ` Krzysztof Kozlowski
2025-10-16 10:22 ` [PATCH 2/3] media: qcom: camss: add support for SM6150 camss Wenmeng Liu
2025-10-16 10:29   ` Bryan O'Donoghue
2025-10-16 12:36     ` Wenmeng Liu [this message]
2025-10-16 13:55       ` Bryan O'Donoghue
2025-10-16 13:43   ` Vladimir Zapolskiy
2025-10-16 10:22 ` [PATCH 3/3] arm64: dts: qcom: sm6150: Add camss node Wenmeng Liu
2025-10-16 13:48   ` Vladimir Zapolskiy
2025-10-22 16:02     ` Konrad Dybcio
2025-11-02 17:47     ` 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=e4be125c-752e-46c9-9637-fe23cbf04b1a@qualcomm.com \
    --to=quic_wenmliu@qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bod@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@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=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=todor.too@gmail.com \
    --cc=vladimir.zapolskiy@linaro.org \
    --cc=wenmeng.liu@oss.qualcomm.com \
    /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