From: Adam Skladowski <a39.skl@gmail.com>
Cc: phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Adam Skladowski <a39.skl@gmail.com>,
Rob Clark <robdclark@gmail.com>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Sean Paul <sean@poorly.run>,
Marijn Suijten <marijn.suijten@somainline.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/1] Split Adreno schemas
Date: Tue, 26 Mar 2024 21:05:57 +0100 [thread overview]
Message-ID: <20240326201140.10561-1-a39.skl@gmail.com> (raw)
Following recommendation from Dmitry Baryshkov this series split schema
into separate schemas per gpu family, as i don't really understand much
of yamls and dt-schema i decided to send this as RFC and if there
are any changes suggested i will be glad if these can be explained
to me in ELI5 format.
Adam Skladowski (1):
dt-bindings: display/msm: gpu: Split Adreno schemas into separate
files
.../devicetree/bindings/display/msm/gpu.yaml | 317 ++----------------
.../bindings/display/msm/qcom,adreno-306.yaml | 115 +++++++
.../bindings/display/msm/qcom,adreno-330.yaml | 111 ++++++
.../bindings/display/msm/qcom,adreno-405.yaml | 135 ++++++++
.../bindings/display/msm/qcom,adreno-506.yaml | 184 ++++++++++
.../bindings/display/msm/qcom,adreno-530.yaml | 161 +++++++++
.../bindings/display/msm/qcom,adreno-540.yaml | 154 +++++++++
.../bindings/display/msm/qcom,adreno-6xx.yaml | 160 +++++++++
.../display/msm/qcom,adreno-common.yaml | 112 +++++++
9 files changed, 1157 insertions(+), 292 deletions(-)
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-306.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-330.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-405.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-506.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-530.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-540.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-6xx.yaml
create mode 100644 Documentation/devicetree/bindings/display/msm/qcom,adreno-common.yaml
--
2.44.0
next reply other threads:[~2024-03-26 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 20:05 Adam Skladowski [this message]
2024-03-26 20:05 ` [RFC PATCH 1/1] dt-bindings: display/msm: gpu: Split Adreno schemas into separate files Adam Skladowski
2024-03-27 9:20 ` Krzysztof Kozlowski
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=20240326201140.10561-1-a39.skl@gmail.com \
--to=a39.skl@gmail.com \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean@poorly.run \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).