From: Conor Dooley <conor@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Peter Denison <openwrt@marshadder.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Imre Kaloz <kaloz@openwrt.org>, Ted Hess <thess@kitschensync.net>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/3] dt-bindings: arm: List more IXP4xx devices
Date: Mon, 9 Oct 2023 18:15:40 +0100 [thread overview]
Message-ID: <20231009-broadways-ream-38ced3364874@spud> (raw)
In-Reply-To: <20231007-ixp4xx-usr8200-v3-2-ec46edd1ff0e@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1944 bytes --]
On Sat, Oct 07, 2023 at 02:15:12PM +0200, Linus Walleij wrote:
> The ixp4xx bindings are lacking some of the devices we have
> out there in the wild, so let's add them.
>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Skip the crazy triplet compatible. There will have to
> be one device tree including the other if this really
> has to be a unique compatible for gemtek,gtwx5715.
> Linksys will clearly be the most prevalent version.
Ok.
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
> ---
> Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml b/Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml
> index 553dcbc70e35..d60792b1d995 100644
> --- a/Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml
> +++ b/Documentation/devicetree/bindings/arm/intel-ixp4xx.yaml
> @@ -16,12 +16,28 @@ properties:
> oneOf:
> - items:
> - enum:
> + - adieng,coyote
> + - arcom,vulcan
> + - dlink,dsm-g600-a
> + - freecom,fsg-3
> + - gateway,7001
> + - gateworks,gw2348
> + - goramo,multilink-router
> + - intel,ixdp425
> + - intel,ixdpg425
> + - iom,nas-100d
> - linksys,nslu2
> + - netgear,wg302v1
> + - netgear,wg302v2
> + - usr,8200
> - welltech,epbx100
> + - linksys,wrv54g
> + - gemtek,gtwx5715
> - const: intel,ixp42x
> - items:
> - enum:
> - gateworks,gw2358
> + - intel,kixrp435
> - const: intel,ixp43x
>
> additionalProperties: true
>
> --
> 2.41.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-10-09 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 12:15 [PATCH v3 0/3] Device tree updates for IXP4xx Linus Walleij
2023-10-07 12:15 ` [PATCH v3 1/3] dt-bindings: Add vendor prefixes Linus Walleij
2023-10-07 12:15 ` [PATCH v3 2/3] dt-bindings: arm: List more IXP4xx devices Linus Walleij
2023-10-09 17:15 ` Conor Dooley [this message]
2023-10-07 12:15 ` [PATCH v3 3/3] ARM: dts: Use only the Linksys compatible for now Linus Walleij
2023-10-10 13:32 ` [PATCH v3 0/3] Device tree updates for IXP4xx Rob Herring
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=20231009-broadways-ream-38ced3364874@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=openwrt@marshadder.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=thess@kitschensync.net \
/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