From: <markus.stockhausen@gmx.de>
To: "'Krzysztof Kozlowski'" <krzk@kernel.org>
Cc: <vkoul@kernel.org>, <kishon@kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-phy@lists.infradead.org>, <devicetree@vger.kernel.org>,
<chris.packham@alliedtelesis.co.nz>
Subject: AW: [PATCH v3 1/2] dt-bindings: phy: add realtek,rtl8380m-serdes
Date: Mon, 14 Oct 2024 12:59:08 +0200 [thread overview]
Message-ID: <004801db1e28$190402e0$4b0c08a0$@gmx.de> (raw)
In-Reply-To: <sck3hvr6vtdsnseyzdoxdwasd47c7m5yzavpyodc7rj3cwbu26@kqxistduok3u>
> -----Ursprüngliche Nachricht-----
> Von: Krzysztof Kozlowski <krzk@kernel.org>
> Gesendet: Montag, 14. Oktober 2024 09:18
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Cc: vkoul@kernel.org; kishon@kernel.org; robh@kernel.org; krzk+dt@kernel.org;
> conor+dt@kernel.org; linux-phy@lists.infradead.org; devicetree@vger.kernel.org;
> chris.packham@alliedtelesis.co.nz
> Betreff: Re: [PATCH v3 1/2] dt-bindings: phy: add realtek,rtl8380m-serdes
>
> On Sat, Oct 12, 2024 at 09:48:33AM -0400, Markus Stockhausen wrote:
> > Add bindings for the SerDes of the Realtek Otto platform. These are
> > MIPS based network Switch SoCs with up to 52 ports divided into four
> > different model lines.
> > ...
> > + reg:
> > + items:
> > + description:
> > + The primary register memory location. On RTL83xx devices this is the
> > + address to the I/O register range, on RTL93xx devices this is the
> > + address of the MDIO style command/data registers.
>
> Not much improved, still missing constraints.
>
> I don't understand why you introduce changes like this.
Hm, two stupid changes in the last two versions. This was only to get some
more meaningfull description there. Not proud of it and somehow lost what
will be right. Looking at other places a simple
reg:
maxItems: 1
should be sufficient. Ok with that?
> > +
> > + "#phy-cells":
> > + const: 4
> > + description:
> > + The first number defines the SerDes to use. The second number a linked
> > + SerDes. E.g. if a octa 1G PHY is attached to two QSGMII SerDes. The third
> > + number is the first switch port this SerDes is working for, the fourth
> > + number is the last switch port the SerDes is working for.
> > +
> > + firmware-name:
> > + maxItems: 1
> > + description:
> > + An alternative name of the SerDes firmware image file located in the
> > + firmware search path. Set to "" to disable firmware loading.
>
> Missing property, not empty string, should rather indicate unneeded firmware.
Indeed more intuitive. Will drop the hardcoded firmware names in the driver
and only load if firmware-name is set.
> > +
> > +examples:
> > + - |
> > + serdes: phy@1b00e780 {
> > + compatible = "realtek,rtl9302b-serdes";
> > + reg = <0x1b0003b0 0x8>;
>
> This does notmatch unit address... and again: this was not an issue in previous version.
> Your new versions of patchset introduce errors and bugs. This is not how the process
> should look like. Review should improve the patch, not reduce its quality.
Agree will fix. This was wrongly mixed when I removed 3 of the
samples as requested by Rob and cleaned the rest afterwards to
have the firmware example.
Markus
next prev parent reply other threads:[~2024-10-14 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-12 13:48 [PATCH v3 0/2] phy: Realtek Otto SerDes: add new driver Markus Stockhausen
2024-10-12 13:48 ` [PATCH v3 1/2] dt-bindings: phy: add realtek,rtl8380m-serdes Markus Stockhausen
2024-10-14 7:18 ` Krzysztof Kozlowski
2024-10-14 10:59 ` markus.stockhausen [this message]
2024-10-12 13:48 ` [PATCH v3 2/2] phy: Realtek Otto SerDes driver Markus Stockhausen
2024-10-15 17:22 ` kernel test robot
2024-10-15 17:22 ` kernel test robot
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='004801db1e28$190402e0$4b0c08a0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@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).