[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61d793e0-f753-4f68-a169-c98336911588@gmail.com>
Date: Sat, 22 Feb 2025 15:59:29 -0800
From: Kyle Hendry <kylehendrydev@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Heiner Kallweit <hkallweit1@...il.com>, Russell King
<linux@...linux.org.uk>, Florian Fainelli <florian.fainelli@...adcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>, Fernández Rojas
<noltari@...il.com>, Jonas Gorski <jonas.gorski@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v2 5/5] dt-bindings: mfd: brcm: add gphy controller to
BCM63268 sysctl
On 2025-02-17 23:35, Krzysztof Kozlowski wrote:
>> + # Child node
>> + type: object
>> + $ref: /schemas/mfd/syscon.yaml
> No, not really... how is syscon a child of other syscon? Isn't the other
> device the syscon?
>
> This looks really fake hardware description, like recent bootlin claim that
> "one register in syscon is device".
I will change the driver to access the register through the main syscon.
Best regards,
Kyle
Powered by blists - more mailing lists