From: Florian Fainelli <f.fainelli@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v2 5/6] net: dsa: microchip: use wakeup-source DT property to enable PME output
Date: Sat, 22 Jul 2023 07:45:35 -0700 [thread overview]
Message-ID: <d40d5a96-e0af-388e-9fd5-c068b0d2896e@gmail.com> (raw)
In-Reply-To: <20230721135501.1464455-6-o.rempel@pengutronix.de>
On 7/21/2023 6:55 AM, Oleksij Rempel wrote:
> KSZ switches with WoL support signals wake event over PME pin. If this
> pin is attached to some external PMIC or System Controller can't be
> described as GPIO, the only way to describe it in the devicetree is to
> use wakeup-source property.
There is a word missing in the above sentence between "System
Controller" and "can't be", and I believe the word is "that".
> So, add support for this property and enable
> PME switch output if this property is present.
A property that "enables" something means that you are using Device Tree
as a way to encode some sort of policy, maybe this is just the wording
here and what you would want to say is that describing the node with a
'wakeup-source' property indicates that the device is wake-up capable,
regardless of the presence/absence of an interrupt parent?
With the commit message reworded:
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2023-07-22 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 13:54 [PATCH net-next v2 0/6] net: dsa: microchip: provide Wake on LAN support Oleksij Rempel
2023-07-21 13:54 ` [PATCH net-next v2 1/6] dt-bindings: net: dsa: microchip: add wakeup-source property Oleksij Rempel
2023-07-21 13:54 ` [PATCH net-next v2 2/6] dt-bindings: net: dsa: microchip: add local-mac-address property support Oleksij Rempel
2023-07-21 13:54 ` [PATCH net-next v2 3/6] net: dsa: microchip: ksz9477: add Wake on LAN support Oleksij Rempel
2023-07-22 14:42 ` Florian Fainelli
2023-07-21 13:54 ` [PATCH net-next v2 4/6] net: dsa: microchip: ksz9477: add Wake on PHY event support Oleksij Rempel
2023-07-22 14:43 ` Florian Fainelli
2023-07-21 13:55 ` [PATCH net-next v2 5/6] net: dsa: microchip: use wakeup-source DT property to enable PME output Oleksij Rempel
2023-07-22 14:45 ` Florian Fainelli [this message]
2023-07-21 13:55 ` [PATCH net-next v2 6/6] net: dsa: microchip: ksz9477: make switch MAC address configurable Oleksij Rempel
2023-07-21 22:09 ` Tristram.Ha
2023-07-22 0:19 ` Vladimir Oltean
2023-07-22 2:37 ` Florian Fainelli
2023-07-22 11:52 ` Andrew Lunn
2023-07-22 1:35 ` [PATCH net-next v2 0/6] net: dsa: microchip: provide Wake on LAN support Jakub Kicinski
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=d40d5a96-e0af-388e-9fd5-c068b0d2896e@gmail.com \
--to=f.fainelli@gmail.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=woojung.huh@microchip.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).