devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Lee Jones <lee@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Burton <paulburton@kernel.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mips@vger.kernel.org
Subject: Re: [PATCH v2 8/8] dt-bindings: mips: img: Add devices binding
Date: Thu, 13 Jun 2024 12:56:43 -0600	[thread overview]
Message-ID: <20240613185643.GA2286020-robh@kernel.org> (raw)
In-Reply-To: <20240612-boston-syscon-v2-8-9f8e1a07fa63@flygoat.com>

On Wed, Jun 12, 2024 at 12:56:27PM +0100, Jiaxun Yang wrote:
> Add devices binding for various Imagination Technologies
> MIPS based Platforms.
> 
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
>  .../devicetree/bindings/mips/img/devices.yaml      | 33 ++++++++++++++++++++++
>  1 file changed, 33 insertions(+)

Please drop the old bindings or at least the portion covered by 
this. That's 
Documentation/devicetree/bindings/mips/img/pistachio-marduk.txt, 
pistachio.txt, and xilfpga.txt. 

Some of the description can go in here. CPU nodes are documented 
elsewhere by schemas already and can be dropped. The boot protocol isn't 
really DT bindings, so that belongs elsewhere if you want to keep it. 
Documentation/arch/mips/ perhaps?

Rob

      parent reply	other threads:[~2024-06-13 18:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 11:56 [PATCH v2 0/8] MIPS: Boston: Fix syscon devicetree binding and node Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 1/8] MIPS: dts: Boston: Add simple-mfd compatible for syscon Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 2/8] MIPS: dts: Boston: Move syscon-reboot node under syscon Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 3/8] MIPS: dts: Boston: Remove unused #interrupt-cells Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 4/8] MIPS: dts: Boston: Add model property Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 5/8] MIPS: dts: Boston: Rename uart node Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 6/8] dt-bindings: mfd: Add img,boston-platform-regs Jiaxun Yang
2024-06-13 19:04   ` Rob Herring
2024-06-13 19:31     ` Jiaxun Yang
2024-06-12 11:56 ` [PATCH v2 7/8] du-bindings: mips: cpu: Add img,mips compatible Jiaxun Yang
2024-06-12 16:39   ` Conor Dooley
2024-06-12 16:59     ` Jiaxun Yang
2024-06-13 18:59       ` Rob Herring
2024-06-13 19:40         ` Jiaxun Yang
2024-06-15 12:28           ` Conor Dooley
2024-06-15 19:16             ` Jiaxun Yang
2024-06-19 18:13               ` Conor Dooley
2024-06-12 11:56 ` [PATCH v2 8/8] dt-bindings: mips: img: Add devices binding Jiaxun Yang
2024-06-12 16:43   ` Conor Dooley
2024-06-12 16:57     ` Jiaxun Yang
2024-06-12 16:59       ` Conor Dooley
2024-06-13 18:56   ` Rob Herring [this message]

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=20240613185643.GA2286020-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).