devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nate Drude <nate.d@variscite.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Eran Matityahu <eran.m@variscite.com>
Subject: Re: [PATCH] dt-bindings: add device tree bindings for mxl-8611x PHY
Date: Thu, 13 Jul 2023 21:06:06 +0200	[thread overview]
Message-ID: <83d4d054-fa17-2d3e-e6bd-bf7416702dbf@kernel.org> (raw)
In-Reply-To: <6e9346b2-e241-a5c5-c74d-36ff98d20258@variscite.com>

On 13/07/2023 15:23, Nate Drude wrote:
> The MXL8611X driver has custom bindings for configuring the LEDs
> and RGMII internal delays. This patch adds the documentation and
> defines necessary to configure it from the device tree.
> 
> Signed-off-by: Nate Drude <nate.d@variscite.com>
> ---
>   .../net/phy/mxl-8611x.txt                     | 37 +++++++++++++++++++
>   include/dt-bindings/net/mxl-8611x.h           | 27 ++++++++++++++
>   2 files changed, 64 insertions(+)
>   create mode 100644 doc/device-tree-bindings/net/phy/mxl-8611x.txt

You did not CC DT maintainers, so kind of funny way to ask them to
review something.

In general I will not provide full review for projects other than Linux.
Submit bindings to the Linux, following proper Linux kernel process, if
you wish them to be fully reviewed.


>   create mode 100644 include/dt-bindings/net/mxl-8611x.h
> 
> diff --git a/doc/device-tree-bindings/net/phy/mxl-8611x.txt 
> b/doc/device-tree-bindings/net/phy/mxl-8611x.txt
> new file mode 100644
> index 00000000000..462fdf61666
> --- /dev/null
> +++ b/doc/device-tree-bindings/net/phy/mxl-8611x.txt
> @@ -0,0 +1,37 @@
> +* MaxLinear MXL8611x PHY Device Tree binding
> +
> +Required properties:
> +- reg: PHY address
> +
> +Optional properties:
> +- mxl-8611x,ledN_cfg: Register configuration for COM_EXT_LED0_CFG,

That's not correct vendor name. Neither property name - underscores are
not allowed. The property itself does not describe any feature or
hardware. We do not program registers in DT.

> +	COM_EXT_LED1_CFG, and COM_EXT_LED2_CFG
> +- mxl-8611x,rx-internal-delay-ps: RGMII RX Clock Delay used only when 
> PHY operates
> +	in RGMII mode with internal delay (phy-mode is 'rgmii-id' or
> +	'rgmii-rxid') in pico-seconds.
> +- mxl-8611x,tx-internal-delay-ps-100m: RGMII TX Clock Delay used only 

Use correct unit suffixes.

> when PHY operates
> +	in 10/100M RGMII mode with internal delay (phy-mode is 'rgmii-id' or
> +	'rgmii-txid') in pico-seconds.
> +- mxl-8611x,tx-internal-delay-ps-1g: RGMII TX Clock Delay used only 
> when PHY operates
> +	in 1G RGMII mode with internal delay (phy-mode is 'rgmii-id' or
> +	'rgmii-txid') in pico-seconds.

Same problem.

> +
> +Example:
> +
> +	ethernet-phy@0 {
> +		reg = <0>;
> +
> +		mxl-8611x,led0_cfg = <(
> +			MXL8611X_LEDX_CFG_LINK_UP_RX_ACT_ON |
> +			MXL8611X_LEDX_CFG_LINK_UP_TX_ACT_ON |
> +			MXL8611X_LEDX_CFG_TRAFFIC_ACT_BLINK_IND
> +		)>;
> +		mxl-8611x,led1_cfg = <(
> +			MXL8611X_LEDX_CFG_LINK_UP_10MB_ON |
> +			MXL8611X_LEDX_CFG_LINK_UP_100MB_ON |
> +			MXL8611X_LEDX_CFG_LINK_UP_1GB_ON
> +		)>;
> +		mxl-8611x,rx-internal-delay-ps = <0>;
> +		mxl-8611x,tx-internal-delay-ps-100m = <2250>;
> +		mxl-8611x,tx-internal-delay-ps-1g = <150>;
> +	};
> diff --git a/include/dt-bindings/net/mxl-8611x.h 
> b/include/dt-bindings/net/mxl-8611x.h
> new file mode 100644
> index 00000000000..cb0ec0f8bd0
> --- /dev/null
> +++ b/include/dt-bindings/net/mxl-8611x.h
> @@ -0,0 +1,27 @@
> +/* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */
> +/*
> + * Device Tree constants for MaxLinear MXL8611x PHYs
> + *
> + * Copyright 2023 Variscite Ltd.
> + * Copyright 2023 MaxLinear Inc.
> + */
> +
> +#ifndef _DT_BINDINGS_MXL_8611X_H
> +#define _DT_BINDINGS_MXL_8611X_H
> +
> +#define MXL8611X_LEDX_CFG_TRAFFIC_ACT_BLINK_IND		(1 << 13)

Register values are not bindings.


Best regards,
Krzysztof


  reply	other threads:[~2023-07-13 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:20 [PATCH] Requesting review of U-Boot mxl-8611x device tree bindings Nate Drude
2023-07-13 13:23 ` [PATCH] dt-bindings: add device tree bindings for mxl-8611x PHY Nate Drude
2023-07-13 19:06   ` Krzysztof Kozlowski [this message]
2023-07-14 12:53     ` Nate Drude
2023-07-16 16:31       ` Krzysztof Kozlowski

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=83d4d054-fa17-2d3e-e6bd-bf7416702dbf@kernel.org \
    --to=krzk@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eran.m@variscite.com \
    --cc=nate.d@variscite.com \
    /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).