From: Depeng Shao <quic_depengs@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <rfoss@kernel.org>,
<todor.too@gmail.com>, <bryan.odonoghue@linaro.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<mchehab@kernel.org>, <quic_yon@quicinc.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2 4/8] media: qcom: camss: Add new params for csid_device
Date: Mon, 25 Mar 2024 20:30:26 +0800 [thread overview]
Message-ID: <6d9a093e-ee4f-4f4d-8883-e17dc8dc8210@quicinc.com> (raw)
In-Reply-To: <f9281370-d3e5-46f7-8031-d5c2c524eeb9@kernel.org>
Hi Krzysztof,
On 3/20/2024 11:53 PM, Krzysztof Kozlowski wrote:
> On 20/03/2024 15:11, Depeng Shao wrote:
>> CSID gen3 has a new register block which is named as
>> CSID top, it controls the output of CSID, since the
>> CSID can connect to SFE or original VFE in CSID gen3.
>> The register update is moved to CSID from VFE in CSID
>> gen3.
>> So, adding top_base and reg_update variables in csid
>> device structure for CSID gen3.
>
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
Thanks, will update it.
>>
>> Signed-off-by: Depeng Shao <quic_depengs@quicinc.com>
>> ---
>> drivers/media/platform/qcom/camss/camss-csid.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/media/platform/qcom/camss/camss-csid.h b/drivers/media/platform/qcom/camss/camss-csid.h
>> index 4a9e5a2d1f92..ca654b007441 100644
>> --- a/drivers/media/platform/qcom/camss/camss-csid.h
>> +++ b/drivers/media/platform/qcom/camss/camss-csid.h
>> @@ -162,7 +162,9 @@ struct csid_device {
>> struct v4l2_subdev subdev;
>> struct media_pad pads[MSM_CSID_PADS_NUM];
>> void __iomem *base;
>> + void __iomem *top_base;
>> u32 irq;
>> + u32 reg_update;
>> char irq_name[30];
>
> This is pointless. The are no users of this!
>
> Sorry, don't add random code here or there without concept.
>
For the old code, they are new concept, since it is new block in the
hardware, I just want to highlight them.
But thanks for the comment, will update the code based on your comment.
> Best regards,
> Krzysztof
>
Thanks,
Depeng
next prev parent reply other threads:[~2024-03-25 12:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 14:11 [PATCH v2 0/8] media: qcom: camss: Add sm8550 support Depeng Shao
2024-03-20 14:11 ` [PATCH v2 1/8] media: qcom: camss: Add CAMSS_8550 enum Depeng Shao
2024-03-20 14:50 ` Bryan O'Donoghue
2024-03-20 15:51 ` Krzysztof Kozlowski
2024-03-20 15:53 ` Bryan O'Donoghue
2024-03-20 15:59 ` Krzysztof Kozlowski
2024-03-20 14:11 ` [PATCH v2 2/8] media: qcom: camss: Add subdev notify support Depeng Shao
2024-03-20 16:08 ` Bryan O'Donoghue
2024-03-20 16:41 ` Gjorgji Rosikopulos (Consultant)
2024-03-20 14:11 ` [PATCH v2 3/8] media: qcom: camss: Add new csiphy driver 2-1-2 Depeng Shao
2024-03-20 15:21 ` Bryan O'Donoghue
2024-03-25 12:15 ` Depeng Shao
2024-03-20 14:11 ` [PATCH v2 4/8] media: qcom: camss: Add new params for csid_device Depeng Shao
2024-03-20 15:26 ` Bryan O'Donoghue
2024-03-20 15:53 ` Krzysztof Kozlowski
2024-03-25 12:30 ` Depeng Shao [this message]
2024-03-20 14:11 ` [PATCH v2 5/8] media: qcom: camss: Add CSID gen3 driver Depeng Shao
2024-03-20 15:40 ` Bryan O'Donoghue
2024-03-20 16:12 ` Bryan O'Donoghue
2024-03-25 13:38 ` Depeng Shao
2024-03-20 14:11 ` [PATCH v2 6/8] media: qcom: camss: Add new VFE driver for SM8550 Depeng Shao
2024-03-20 15:57 ` Bryan O'Donoghue
2024-03-25 12:47 ` Depeng Shao
2024-04-09 13:39 ` Bryan O'Donoghue
2024-04-09 15:35 ` Bryan O'Donoghue
2024-03-20 14:11 ` [PATCH v2 7/8] media: qcom: camss: Add sm8550 resources Depeng Shao
2024-03-20 15:50 ` Krzysztof Kozlowski
2024-03-20 14:11 ` [PATCH v2 8/8] media: qcom: camss: Add sm8550 support Depeng Shao
2024-03-20 16:01 ` Bryan O'Donoghue
2024-03-25 13:16 ` Depeng Shao
2024-03-20 15:08 ` [PATCH v2 0/8] " Bryan O'Donoghue
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=6d9a093e-ee4f-4f4d-8883-e17dc8dc8210@quicinc.com \
--to=quic_depengs@quicinc.com \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=konrad.dybcio@linaro.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_yon@quicinc.com \
--cc=rfoss@kernel.org \
--cc=todor.too@gmail.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