From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linusw@kernel.org>, Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Marek Vasut <marex@denx.de>,
Lubomir Rintel <lkundrak@v3.sk>, - <devicetree@vger.kernel.org>,
Marc Zyngier <maz@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, linux-serial@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v2 1/3] dt-bindings: intel,ixp4xx-expansion-bus: split out peripheral properties
Date: Mon, 30 Jan 2023 13:12:15 -0600 [thread overview]
Message-ID: <20230130191215.GA3125737-robh@kernel.org> (raw)
In-Reply-To: <20230127093217.60818-2-krzysztof.kozlowski@linaro.org>
On Fri, Jan 27, 2023 at 10:32:15AM +0100, Krzysztof Kozlowski wrote:
> The properties of devices in IXP4xx expansion bus need to be also
> applied to actual devices' bindings. Prepare for this by splitting them
> to separate intel,ixp4xx-expansion-peripheral-props binding, just like
> other memory-controller peripheral properties.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> ...intel,ixp4xx-expansion-bus-controller.yaml | 64 +--------------
> ...tel,ixp4xx-expansion-peripheral-props.yaml | 80 +++++++++++++++++++
Kind of odd to have these in 2 directories. Can we move
intel,ixp4xx-expansion-bus-controller.yaml to
bindings/memory-controllers/?
Or maybe all the external/parallel bus interfaces need their own
directory?
> .../mc-peripheral-props.yaml | 1 +
> 3 files changed, 82 insertions(+), 63 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml
>
> diff --git a/Documentation/devicetree/bindings/bus/intel,ixp4xx-expansion-bus-controller.yaml b/Documentation/devicetree/bindings/bus/intel,ixp4xx-expansion-bus-controller.yaml
> index 5fb4e7bfa4da..a771796ec499 100644
> --- a/Documentation/devicetree/bindings/bus/intel,ixp4xx-expansion-bus-controller.yaml
> +++ b/Documentation/devicetree/bindings/bus/intel,ixp4xx-expansion-bus-controller.yaml
> @@ -56,69 +56,7 @@ patternProperties:
> description: Devices attached to chip selects are represented as
> subnodes.
> type: object
> -
> - properties:
> - intel,ixp4xx-eb-t1:
> - description: Address timing, extend address phase with n cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - maximum: 3
> -
> - intel,ixp4xx-eb-t2:
> - description: Setup chip select timing, extend setup phase with n cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - maximum: 3
> -
> - intel,ixp4xx-eb-t3:
> - description: Strobe timing, extend strobe phase with n cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - maximum: 15
> -
> - intel,ixp4xx-eb-t4:
> - description: Hold timing, extend hold phase with n cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - maximum: 3
> -
> - intel,ixp4xx-eb-t5:
> - description: Recovery timing, extend recovery phase with n cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - maximum: 15
> -
> - intel,ixp4xx-eb-cycle-type:
> - description: The type of cycles to use on the expansion bus for this
> - chip select. 0 = Intel cycles, 1 = Motorola cycles, 2 = HPI cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1, 2]
> -
> - intel,ixp4xx-eb-byte-access-on-halfword:
> - description: Allow byte read access on half word devices.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> -
> - intel,ixp4xx-eb-hpi-hrdy-pol-high:
> - description: Set HPI HRDY polarity to active high when using HPI.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> -
> - intel,ixp4xx-eb-mux-address-and-data:
> - description: Multiplex address and data on the data bus.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> -
> - intel,ixp4xx-eb-ahb-split-transfers:
> - description: Enable AHB split transfers.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> -
> - intel,ixp4xx-eb-write-enable:
> - description: Enable write cycles.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> -
> - intel,ixp4xx-eb-byte-access:
> - description: Expansion bus uses only 8 bits. The default is to use
> - 16 bits.
> - $ref: /schemas/types.yaml#/definitions/uint32
> - enum: [0, 1]
> + $ref: /schemas/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml#
>
> required:
> - compatible
> diff --git a/Documentation/devicetree/bindings/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml b/Documentation/devicetree/bindings/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml
> new file mode 100644
> index 000000000000..8f782c80e88b
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml
> @@ -0,0 +1,80 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Peripheral properties for Intel IXP4xx Expansion Bus
> +
> +description: |
Don't need '|'.
> + The IXP4xx expansion bus controller handles access to devices on the
> + memory-mapped expansion bus on the Intel IXP4xx family of system on chips,
> + including IXP42x, IXP43x, IXP45x and IXP46x.
> +
> +maintainers:
> + - Linus Walleij <linus.walleij@linaro.org>
> +
> +properties:
> + intel,ixp4xx-eb-t1:
> + description: Address timing, extend address phase with n cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 3
> +
> + intel,ixp4xx-eb-t2:
> + description: Setup chip select timing, extend setup phase with n cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 3
> +
> + intel,ixp4xx-eb-t3:
> + description: Strobe timing, extend strobe phase with n cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 15
> +
> + intel,ixp4xx-eb-t4:
> + description: Hold timing, extend hold phase with n cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 3
> +
> + intel,ixp4xx-eb-t5:
> + description: Recovery timing, extend recovery phase with n cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + maximum: 15
> +
> + intel,ixp4xx-eb-cycle-type:
> + description: The type of cycles to use on the expansion bus for this
> + chip select. 0 = Intel cycles, 1 = Motorola cycles, 2 = HPI cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1, 2]
> +
> + intel,ixp4xx-eb-byte-access-on-halfword:
> + description: Allow byte read access on half word devices.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> + intel,ixp4xx-eb-hpi-hrdy-pol-high:
> + description: Set HPI HRDY polarity to active high when using HPI.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> + intel,ixp4xx-eb-mux-address-and-data:
> + description: Multiplex address and data on the data bus.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> + intel,ixp4xx-eb-ahb-split-transfers:
> + description: Enable AHB split transfers.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> + intel,ixp4xx-eb-write-enable:
> + description: Enable write cycles.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> + intel,ixp4xx-eb-byte-access:
> + description: Expansion bus uses only 8 bits. The default is to use
> + 16 bits.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1]
> +
> +additionalProperties: true
> diff --git a/Documentation/devicetree/bindings/memory-controllers/mc-peripheral-props.yaml b/Documentation/devicetree/bindings/memory-controllers/mc-peripheral-props.yaml
> index 53ae995462db..5acfcad12bb7 100644
> --- a/Documentation/devicetree/bindings/memory-controllers/mc-peripheral-props.yaml
> +++ b/Documentation/devicetree/bindings/memory-controllers/mc-peripheral-props.yaml
> @@ -34,5 +34,6 @@ required:
> # The controller specific properties go here.
> allOf:
> - $ref: st,stm32-fmc2-ebi-props.yaml#
> + - $ref: intel,ixp4xx-expansion-peripheral-props.yaml#
>
> additionalProperties: true
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-01-30 19:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:32 [PATCH v2 0/3] dt-bindings: serial/mtd/mc/ata: use MC peripheral props Krzysztof Kozlowski
2023-01-27 9:32 ` [PATCH v2 1/3] dt-bindings: intel,ixp4xx-expansion-bus: split out peripheral properties Krzysztof Kozlowski
2023-01-27 13:23 ` Linus Walleij
2023-01-30 19:12 ` Rob Herring [this message]
2023-02-06 8:41 ` Krzysztof Kozlowski
2023-01-27 9:32 ` [PATCH v2 2/3] dt-bindings: reference MC peripheral properties in relevant devices Krzysztof Kozlowski
2023-01-27 13:24 ` Linus Walleij
2023-01-28 0:54 ` Damien Le Moal
2023-01-30 9:24 ` Miquel Raynal
2023-01-27 9:32 ` [PATCH v2 3/3] dt-bindings: serial: restrict possible child node names Krzysztof Kozlowski
2023-01-27 13:29 ` Linus Walleij
2023-01-29 15:48 ` Krzysztof Kozlowski
2023-01-30 22:42 ` Linus Walleij
2023-02-02 10:50 ` [PATCH v2 0/3] dt-bindings: serial/mtd/mc/ata: use MC peripheral props Greg Kroah-Hartman
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=20230130191215.GA3125737-robh@kernel.org \
--to=robh@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkundrak@v3.sk \
--cc=marex@denx.de \
--cc=maz@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=wim@linux-watchdog.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).