From: Robert Foss <robert.foss@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org,
robert.foss@linaro.org, todor.too@gmail.com, mchehab@kernel.org,
robh+dt@kernel.org, angelogioacchino.delregno@somainline.org,
linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Andrey Konovalov <andrey.konovalov@linaro.org>,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH v3 0/4] Remove clock-lanes DT property from CAMSS
Date: Thu, 18 Nov 2021 13:48:15 +0100 [thread overview]
Message-ID: <20211118124819.1902427-1-robert.foss@linaro.org> (raw)
Changes since v2:
- Stephan: Rebased on v5.16-rc1
- Stephan: Fixed 3/4 commit message title
Changes since v1:
- Rob: Instead of documenting and fixing the use of the clock-lanes
property, remove it, since it is is not programmable and
therefore shouldn't be exposed in the DT.
Robert Foss (4):
media: camss: csiphy: Move to hardcode CSI Clock Lane number
media: dt-bindings: media: camss: Remove clock-lane property
arm64: dts: qcom: apq8016-sbc: Remove clock-lanes property from &camss
node
arm64: dts: qcom: sdm845-db845c: Remove clock-lanes property from
&camss node
.../bindings/media/qcom,msm8916-camss.yaml | 10 ---------
.../bindings/media/qcom,msm8996-camss.yaml | 20 ------------------
.../bindings/media/qcom,sdm660-camss.yaml | 20 ------------------
.../bindings/media/qcom,sdm845-camss.yaml | 17 ---------------
arch/arm64/boot/dts/qcom/apq8016-sbc.dts | 2 --
arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 3 ---
.../qcom/camss/camss-csiphy-2ph-1-0.c | 19 +++++++++++++++--
.../qcom/camss/camss-csiphy-3ph-1-0.c | 17 ++++++++++++++-
.../media/platform/qcom/camss/camss-csiphy.c | 21 +------------------
.../media/platform/qcom/camss/camss-csiphy.h | 7 +++++++
10 files changed, 41 insertions(+), 95 deletions(-)
--
2.32.0
next reply other threads:[~2021-11-18 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 12:48 Robert Foss [this message]
2021-11-18 12:48 ` [PATCH v3 1/4] media: camss: csiphy: Move to hardcode CSI Clock Lane number Robert Foss
2021-11-19 4:01 ` Bjorn Andersson
2021-12-06 15:04 ` Bjorn Andersson
2021-11-18 12:48 ` [PATCH v3 2/4] media: dt-bindings: media: camss: Remove clock-lane property Robert Foss
2021-11-19 4:05 ` Bjorn Andersson
2021-11-29 0:21 ` Rob Herring
2021-12-06 15:05 ` Bjorn Andersson
2021-11-18 12:48 ` [PATCH v3 3/4] arm64: dts: qcom: apq8016-sbc: Remove clock-lanes property from &camss node Robert Foss
2021-12-06 15:06 ` Bjorn Andersson
2021-12-06 15:13 ` Robert Foss
2021-11-18 12:48 ` [PATCH v3 4/4] arm64: dts: qcom: sdm845-db845c: " Robert Foss
2021-12-06 15:07 ` 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=20211118124819.1902427-1-robert.foss@linaro.org \
--to=robert.foss@linaro.org \
--cc=agross@kernel.org \
--cc=andrey.konovalov@linaro.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.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=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--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).