From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jerome Brunet <jbrunet@baylibre.com>,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Cc: linux-amlogic@lists.infradead.org,
Kevin Hilman <khilman@baylibre.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Da Xue <da@lessconfused.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] dt-bindings: net: add amlogic gxl mdio multiplexer
Date: Tue, 17 Jan 2023 09:31:48 +0100 [thread overview]
Message-ID: <4be60ea2-cb67-7695-1144-bf39453e9e1f@kernel.org> (raw)
In-Reply-To: <20230116091637.272923-2-jbrunet@baylibre.com>
On 16/01/2023 10:16, Jerome Brunet wrote:
> Add documentation for the MDIO bus multiplexer found on the Amlogic GXL
> SoC family
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.
>
> Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
> ---
> .../bindings/net/amlogic,gxl-mdio-mux.yaml | 64 +++++++++++++++++++
> 1 file changed, 64 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/amlogic,gxl-mdio-mux.yaml
>
> diff --git a/Documentation/devicetree/bindings/net/amlogic,gxl-mdio-mux.yaml b/Documentation/devicetree/bindings/net/amlogic,gxl-mdio-mux.yaml
> new file mode 100644
> index 000000000000..d21bce695fa9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/amlogic,gxl-mdio-mux.yaml
> @@ -0,0 +1,64 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/net/amlogic,gxl-mdio-mux.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Amlogic GXL MDIO bus multiplexer
> +
> +maintainers:
> + - Jerome Brunet <jbrunet@baylibre.com>
> +
> +description:
> + This is a special case of a MDIO bus multiplexer. It allows to choose between
> + the internal mdio bus leading to the embedded 10/100 PHY or the external
> + MDIO bus on the Amlogic GXL SoC family.
> +
> +allOf:
> + - $ref: mdio-mux.yaml#
> +
> +properties:
> + compatible:
> + const: amlogic,gxl-mdio-mux
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: ref
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + eth_phy_mux: mdio@558 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "amlogic,gxl-mdio-mux";
compatible, then reg then the rest.
> + clocks = <&refclk>;
> + clock-names = "ref";
> + reg = <0x558 0xc>;
> + mdio-parent-bus = <&mdio0>;
> +
> + external_mdio: mdio@0 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x0>;
reg is before other properties.
> + };
> +
> + internal_mdio: mdio@1 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x1>;
Ditto. If you resend, keep my tag and finally use get_maintainers.pl
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-17 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 9:16 [PATCH net-next 0/2] net: mdio: add amlogic gxl mdio mux support Jerome Brunet
2023-01-16 9:16 ` [PATCH net-next 1/2] dt-bindings: net: add amlogic gxl mdio multiplexer Jerome Brunet
2023-01-17 8:31 ` Krzysztof Kozlowski [this message]
2023-01-17 9:05 ` Jerome Brunet
2023-01-17 10:39 ` Krzysztof Kozlowski
2023-01-16 9:16 ` [PATCH net-next 2/2] net: mdio: add amlogic gxl mdio mux support Jerome Brunet
2023-01-16 12:11 ` Simon Horman
2023-01-16 13:27 ` Jerome Brunet
2023-01-16 13:51 ` Simon Horman
2023-01-18 2:56 ` Andrew Lunn
2023-01-18 12:41 ` Simon Horman
2023-01-18 3:02 ` Andrew Lunn
2023-01-19 10:55 ` Jerome Brunet
2023-01-19 17:17 ` Andrew Lunn
2023-01-20 10:16 ` Jerome Brunet
2023-01-18 3:08 ` [PATCH net-next 0/2] " Andrew Lunn
2023-01-19 10:42 ` Jerome Brunet
2023-01-19 17:21 ` Andrew Lunn
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=4be60ea2-cb67-7695-1144-bf39453e9e1f@kernel.org \
--to=krzk@kernel.org \
--cc=da@lessconfused.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.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).