From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: [GIT PULL] Devicetree fixes for v6.14, part 1
Date: Sat, 15 Feb 2025 18:03:25 -0600 [thread overview]
Message-ID: <20250216000325.GA1688225-robh@kernel.org> (raw)
Linus,
Please pull a couple of DT fixes. Well, a few are things that fell thru
the cracks for the merge window.
Rob
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-6.14-1
for you to fetch changes up to 038e33fcd40e59b60cdca561c2a39998e6759e08:
dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description (2025-02-05 12:39:30 -0600)
----------------------------------------------------------------
Devicetree fixes for v6.14:
- Add bindings for QCom QCS8300 clocks, QCom SAR2130P qfprom,
powertip,{st7272|hx8238a} displays,
- Fix compatible for TI am62a7 dss
- Add a kunit test for __of_address_resource_bounds()
----------------------------------------------------------------
Devarsh Thakkar (1):
dt-bindings: display: ti: Fix compatible for am62a7 dss
Dmitry Baryshkov (1):
dt-bindings: nvmem: qcom,qfprom: Add SAR2130P compatible
Imran Shaik (3):
dt-bindings: clock: qcom: Add GPU clocks for QCS8300
dt-bindings: clock: qcom: Add CAMCC clocks for QCS8300
dt-bindings: clock: qcom: Add QCS8300 video clock controller
Lukasz Majewski (1):
dt-bindings: display: Add powertip,{st7272|hx8238a} as DT Schema description
Thomas Weißschuh (1):
of: address: Add kunit test for __of_address_resource_bounds()
.../devicetree/bindings/clock/qcom,gpucc.yaml | 3 +
.../bindings/clock/qcom,sa8775p-camcc.yaml | 6 +-
.../bindings/clock/qcom,sa8775p-videocc.yaml | 1 +
.../bindings/display/panel/powertip,hx8238a.yaml | 29 +++++
.../bindings/display/panel/powertip,st7272.yaml | 29 +++++
.../bindings/display/ti/ti,am65x-dss.yaml | 2 +-
.../devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
drivers/of/address.c | 5 +-
drivers/of/of_private.h | 4 +
drivers/of/of_test.c | 119 ++++++++++++++++++++-
include/dt-bindings/clock/qcom,qcs8300-camcc.h | 16 +++
include/dt-bindings/clock/qcom,qcs8300-gpucc.h | 17 +++
12 files changed, 228 insertions(+), 4 deletions(-)
create mode 100644 Documentation/devicetree/bindings/display/panel/powertip,hx8238a.yaml
create mode 100644 Documentation/devicetree/bindings/display/panel/powertip,st7272.yaml
create mode 100644 include/dt-bindings/clock/qcom,qcs8300-camcc.h
create mode 100644 include/dt-bindings/clock/qcom,qcs8300-gpucc.h
next reply other threads:[~2025-02-16 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 0:03 Rob Herring [this message]
2025-02-16 1:30 ` [GIT PULL] Devicetree fixes for v6.14, part 1 pr-tracker-bot
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=20250216000325.GA1688225-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=saravanak@google.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox