devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Frank Rowand <frowand.list@gmail.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.6, take 1
Date: Thu, 7 Sep 2023 13:26:24 -0500	[thread overview]
Message-ID: <20230907182624.GA1977731-robh@kernel.org> (raw)

Linus,

Please pull. A couple of conversions which didn't get picked up by the  
subsystems and 1 fix.

Rob


The following changes since commit 75cc186739805a5e8abe133be04692b36e7a5257:

  dt-bindings: usb: Add V3s compatible string for OHCI (2023-08-28 16:36:52 -0500)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git tags/devicetree-fixes-for-6.6-1

for you to fetch changes up to 591b00cc4fcfcb4532e4b85b5b2e67bbcf4973a0:

  dt-bindings: irqchip: convert st,stih407-irq-syscfg to DT schema (2023-09-05 16:15:09 -0500)

----------------------------------------------------------------
Devicetree fixes for v6.6, part 1:

- Convert st,stih407-irq-syscfg and Omnivision OV7251 bindings to DT
  schema

- Merge Omnivision OV5695 into OV5693 binding

- Fix of_overlay_fdt_apply prototype when !CONFIG_OF_OVERLAY

----------------------------------------------------------------
Pavel Pisa (1):
      of: overlay: Fix of_overlay_fdt_apply prototype when !CONFIG_OF_OVERLAY

Raphael Gallais-Pou (1):
      dt-bindings: irqchip: convert st,stih407-irq-syscfg to DT schema

Rob Herring (2):
      media: dt-bindings: Merge OV5695 into OV5693 binding
      media: dt-bindings: Convert Omnivision OV7251 to DT schema

 .../devicetree/bindings/i2c/qcom,i2c-cci.yaml      |   1 +
 .../interrupt-controller/st,sti-irq-syscfg.txt     |  30 ------
 .../st,stih407-irq-syscfg.yaml                     |  65 ++++++++++++
 .../devicetree/bindings/media/i2c/ov5695.txt       |  41 --------
 .../devicetree/bindings/media/i2c/ov7251.txt       |  52 ----------
 .../devicetree/bindings/media/i2c/ovti,ov5693.yaml |  31 ++++--
 .../devicetree/bindings/media/i2c/ovti,ov7251.yaml | 109 +++++++++++++++++++++
 .../devicetree/bindings/media/rockchip-isp1.yaml   |   1 +
 include/linux/of.h                                 |   4 +-
 9 files changed, 202 insertions(+), 132 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/st,sti-irq-syscfg.txt
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/st,stih407-irq-syscfg.yaml
 delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov5695.txt
 delete mode 100644 Documentation/devicetree/bindings/media/i2c/ov7251.txt
 create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ov7251.yaml

             reply	other threads:[~2023-09-07 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 18:26 Rob Herring [this message]
2023-09-08  1:25 ` [GIT PULL] Devicetree fixes for v6.6, take 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=20230907182624.GA1977731-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).