linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "lee@kernel.org" <lee@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH v4 3/3] dt-bindings: mfd: Add more RTL9300 variants
Date: Wed, 25 Sep 2024 09:20:25 +0200	[thread overview]
Message-ID: <29f8c438-6e4a-4c1f-b68b-5f7d1bd0235e@kernel.org> (raw)
In-Reply-To: <0886f3fb-4e05-4787-aecc-5a5b8a3b8d73@alliedtelesis.co.nz>

On 24/09/2024 22:59, Chris Packham wrote:
> 
> On 24/09/24 20:40, Krzysztof Kozlowski wrote:
>> On Tue, Sep 24, 2024 at 10:57:19AM +1200, Chris Packham wrote:
>>> Add the RTL9301, RTL9300B and RTL9303. These have the same SoC as the
>>> RTL9302C but differ in the Ethernet switch/SERDES arrangement.
>>>
>>> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
>>> ---
>>>
>>> Notes:
>>>      Changes in v4:
>>>      - New
>>>
>>>   .../devicetree/bindings/mfd/realtek,rtl9302c-switch.yaml       | 3 +++
>>>   1 file changed, 3 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/mfd/realtek,rtl9302c-switch.yaml b/Documentation/devicetree/bindings/mfd/realtek,rtl9302c-switch.yaml
>>> index 2d20dd07a7e9..a3ba6d9bacaa 100644
>>> --- a/Documentation/devicetree/bindings/mfd/realtek,rtl9302c-switch.yaml
>>> +++ b/Documentation/devicetree/bindings/mfd/realtek,rtl9302c-switch.yaml
>>> @@ -18,7 +18,10 @@ properties:
>>>     compatible:
>>>       items:
>>>         - enum:
>>> +          - realtek,rtl9301-switch
>>> +          - realtek,rtl9302b-switch
>>>             - realtek,rtl9302c-switch
>>> +          - realtek,rtl9303-switch
>> This should be squashed. One logical change is to add a new binding for
>> entire family, not device-by-device.
> Yes I did consider that. The main thing that gave me pause for thought 
> was the file naming thing. If I squash this should I switch back to the 
> realtek,rtl9300-switch filename? I'll probably add the 
> realtek,rtl9300-switch fallback as well (and add the chip specific 
> compatibles for the i2c).

Splitting this per patch did not solve it - following your logic, file
should be renamed.

Choose name matching one compatible, e.g. the fallback. Aren't all these
devices compatible?

Best regards,
Krzysztof


      reply	other threads:[~2024-09-25  7:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-23 22:57 [PATCH v4 0/3] mips: realtek: Add reboot support Chris Packham
2024-09-23 22:57 ` [PATCH v4 1/3] dt-bindings: mfd: Add Realtek switch Chris Packham
2024-09-24  8:39   ` Krzysztof Kozlowski
2024-09-24  8:51     ` Krzysztof Kozlowski
2024-09-24 20:56       ` Chris Packham
2024-09-24 22:16         ` [RFC PATCH v4.5] dt-bindings: mfd: Add Realtek RTL9300 switch peripherals Chris Packham
2024-09-24 23:21           ` Rob Herring (Arm)
2024-09-25  7:25           ` Krzysztof Kozlowski
2024-09-25  8:08         ` [PATCH v4 1/3] dt-bindings: mfd: Add Realtek switch Krzysztof Kozlowski
2024-09-23 22:57 ` [PATCH v4 2/3] mips: dts: realtek: Add syscon-reboot node Chris Packham
2024-09-24  8:40   ` Krzysztof Kozlowski
2024-09-23 22:57 ` [PATCH v4 3/3] dt-bindings: mfd: Add more RTL9300 variants Chris Packham
2024-09-24  8:40   ` Krzysztof Kozlowski
2024-09-24 20:59     ` Chris Packham
2024-09-25  7:20       ` Krzysztof Kozlowski [this message]

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=29f8c438-6e4a-4c1f-b68b-5f7d1bd0235e@kernel.org \
    --to=krzk@kernel.org \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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).