From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Richard Acayan <mailingradian@gmail.com>,
Loic Poulain <loic.poulain@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Todor Tomov <todor.too@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v3 3/5] media: qcom: camss: add support for SDM670 camss
Date: Tue, 20 Aug 2024 10:45:40 +0100 [thread overview]
Message-ID: <f1c33879-c1ef-4861-be02-bcddd713de4b@linaro.org> (raw)
In-Reply-To: <20240819221051.31489-10-mailingradian@gmail.com>
On 19/08/2024 23:10, Richard Acayan wrote:
> The camera subsystem for the SDM670 the same as on SDM845 except with
> 3 CSIPHY ports instead of 4. Add support for the SDM670 camera
> subsystem.
>
> Signed-off-by: Richard Acayan <mailingradian@gmail.com>
> ---
> drivers/media/platform/qcom/camss/camss.c | 191 ++++++++++++++++++++++
> 1 file changed, 191 insertions(+)
>
> diff --git a/drivers/media/platform/qcom/camss/camss.c b/drivers/media/platform/qcom/camss/camss.c
> index 51b1d3550421..b2f22bfd8692 100644
> --- a/drivers/media/platform/qcom/camss/camss.c
> +++ b/drivers/media/platform/qcom/camss/camss.c
Reviewed-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Acked-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
next prev parent reply other threads:[~2024-08-20 9:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 22:10 [PATCH v3 0/5] Add SDM670 camera subsystem Richard Acayan
2024-08-19 22:10 ` [PATCH v3 1/5] dt-bindings: i2c: qcom-cci: Document SDM670 compatible Richard Acayan
2024-08-20 6:23 ` Krzysztof Kozlowski
2024-08-20 8:40 ` Vladimir Zapolskiy
2024-08-19 22:10 ` [PATCH v3 2/5] dt-bindings: media: camss: Add qcom,sdm670-camss Richard Acayan
2024-08-20 7:31 ` Krzysztof Kozlowski
2024-08-20 9:15 ` Vladimir Zapolskiy
2024-08-20 9:56 ` Krzysztof Kozlowski
2024-08-20 11:37 ` Vladimir Zapolskiy
2024-08-19 22:10 ` [PATCH v3 3/5] media: qcom: camss: add support for SDM670 camss Richard Acayan
2024-08-20 9:45 ` Bryan O'Donoghue [this message]
2024-08-21 8:15 ` Vladimir Zapolskiy
2024-08-19 22:10 ` [PATCH v3 4/5] arm64: dts: qcom: sdm670: add camcc Richard Acayan
2024-08-20 9:23 ` Vladimir Zapolskiy
2024-08-20 9:26 ` Konrad Dybcio
2024-08-19 22:10 ` [PATCH v3 5/5] arm64: dts: qcom: sdm670: add camss and cci Richard Acayan
2024-08-20 9:40 ` Bryan O'Donoghue
2024-08-21 10:40 ` Vladimir Zapolskiy
2024-08-23 23:44 ` Richard Acayan
2024-08-24 11:56 ` Bryan O'Donoghue
2024-08-24 11:59 ` [PATCH] i2c: qcom-cci: Stop complaining about DT set clock rate Bryan O'Donoghue
2024-08-24 12:39 ` Vladimir Zapolskiy
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=f1c33879-c1ef-4861-be02-bcddd713de4b@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@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-i2c@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mailingradian@gmail.com \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).