From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org,
robh+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Cc: dmitry.baryshkov@linaro.org, jonathan@marek.ca, hfink@snap.com,
jgrahsl@snap.com, bryan.odonoghue@linaro.org
Subject: [PATCH 0/4] Add camss to SM8250 dtsi
Date: Sat, 9 Apr 2022 17:45:52 +0100 [thread overview]
Message-ID: <20220409164556.2832782-1-bryan.odonoghue@linaro.org> (raw)
Add in necessary CAMSS, pin and CCI definitions to the SM8250 dtsi.
This is the SoC specific stuff, the platform enablement will be done in a
separate drop later.
On the RB5 platform we have validated ~ 30 FPS @ 4K using the SRGGB10P
pixel format provided by a Sony IMX577 sensor.
Link: https://git.linaro.org/people/bryan.odonoghue/kernel.git/log/?h=br-v5.19b%2brb5-dts%2bsensors
Bryan O'Donoghue (4):
arm64: dts: qcom: sm8250: Add camcc DT node
arm64: dts: qcom: sm8250: camss: Add CAMSS block definition
arm64: dts: qcom: sm8250: camss: Add downstream camera pin definitions
arm64: dts: qcom: sm8250: camss: Add CCI definitions
arch/arm64/boot/dts/qcom/sm8250.dtsi | 721 +++++++++++++++++++++++++++
1 file changed, 721 insertions(+)
--
2.35.1
next reply other threads:[~2022-04-09 16:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-09 16:45 Bryan O'Donoghue [this message]
2022-04-09 16:45 ` [PATCH 1/4] arm64: dts: qcom: sm8250: Add camcc DT node Bryan O'Donoghue
2022-04-09 16:45 ` [PATCH 2/4] arm64: dts: qcom: sm8250: camss: Add CAMSS block definition Bryan O'Donoghue
2022-04-12 2:07 ` Bjorn Andersson
2022-04-09 16:45 ` [PATCH 3/4] arm64: dts: qcom: sm8250: camss: Add downstream camera pin definitions Bryan O'Donoghue
2022-04-12 2:04 ` Bjorn Andersson
2022-04-12 23:50 ` Bryan O'Donoghue
2022-04-09 16:45 ` [PATCH 4/4] arm64: dts: qcom: sm8250: camss: Add CCI definitions Bryan O'Donoghue
2022-04-12 2:06 ` Bjorn Andersson
2022-04-12 23:58 ` Bryan O'Donoghue
2022-04-13 1:08 ` 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=20220409164556.2832782-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=hfink@snap.com \
--cc=jgrahsl@snap.com \
--cc=jonathan@marek.ca \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.