From: Richard Acayan <mailingradian@gmail.com>
To: 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>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
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
Cc: Richard Acayan <mailingradian@gmail.com>
Subject: [PATCH v2 0/5] Add SDM670 camera subsystem
Date: Tue, 13 Aug 2024 19:00:39 -0400 [thread overview]
Message-ID: <20240813230037.84004-8-mailingradian@gmail.com> (raw)
This adds support for the camera subsystem on the Snapdragon 670.
Changes since v1 (20240806224219.71623-7-mailingradian@gmail.com):
- define dedicated resource structs/arrays for sdm670 (3/5)
- separate camcc device tree node into its own patch (4/5)
- specify correct dual license (2/5)
- add include directives in dt-bindings camss example (2/5)
- remove src clocks from dt-bindings (2/5)
- remove src clocks from dtsi (5/5)
- add power-domain-names to camss (5/5)
- specify power domain names (3/5)
- restrict cci-i2c clocks (1/5)
- populate a commit message with hw info (2/5)
- reword commit message (3/5)
Richard Acayan (5):
dt-bindings: i2c: qcom-cci: Document SDM670 compatible
dt-bindings: media: camss: Add qcom,sdm670-camss
media: camss: add support for SDM670 camss
arm64: dts: qcom: sdm670: add camcc
arm64: dts: qcom: sdm670: add camss and cci
.../devicetree/bindings/i2c/qcom,i2c-cci.yaml | 2 +
.../bindings/media/qcom,sdm670-camss.yaml | 324 ++++++++++++++++++
arch/arm64/boot/dts/qcom/sdm670.dtsi | 203 +++++++++++
drivers/media/platform/qcom/camss/camss.c | 194 +++++++++++
4 files changed, 723 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/qcom,sdm670-camss.yaml
--
2.46.0
next reply other threads:[~2024-08-13 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 23:00 Richard Acayan [this message]
2024-08-13 23:00 ` [PATCH v2 1/5] dt-bindings: i2c: qcom-cci: Document SDM670 compatible Richard Acayan
2024-08-14 8:40 ` Bryan O'Donoghue
2024-08-18 15:15 ` Rob Herring (Arm)
2024-08-13 23:00 ` [PATCH v2 2/5] dt-bindings: media: camss: Add qcom,sdm670-camss Richard Acayan
2024-08-14 0:26 ` Rob Herring (Arm)
2024-08-13 23:00 ` [PATCH v2 3/5] media: camss: add support for SDM670 camss Richard Acayan
2024-08-14 8:38 ` Bryan O'Donoghue
2024-08-13 23:00 ` [PATCH v2 4/5] arm64: dts: qcom: sdm670: add camcc Richard Acayan
2024-08-14 8:31 ` Bryan O'Donoghue
2024-08-13 23:00 ` [PATCH v2 5/5] arm64: dts: qcom: sdm670: add camss and cci Richard Acayan
2024-08-14 8:30 ` 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=20240813230037.84004-8-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=bryan.odonoghue@linaro.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=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