[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231027190910.27044-1-luizluca@gmail.com>
Date: Fri, 27 Oct 2023 16:00:54 -0300
From: Luiz Angelo Daros de Luca <luizluca@...il.com>
To: netdev@...r.kernel.org
Cc: linus.walleij@...aro.org,
alsi@...g-olufsen.dk,
andrew@...n.ch,
vivien.didelot@...il.com,
f.fainelli@...il.com,
olteanv@...il.com,
davem@...emloft.net,
kuba@...nel.org,
pabeni@...hat.com,
robh+dt@...nel.org,
krzk+dt@...nel.org,
arinc.unal@...nc9.com
Subject: [PATCH net-next v2 0/3] net: dsa: realtek: support reset controller
v1->v2:
- Introduce a dedicated commit for removing the reset-gpios requirement.
- Place bindings patches before code changes.
- Remove the 'reset-names' property.
- Move the example from the commit message to realtek.yaml.
- Split the reset function into _assert/_deassert variants.
- Modify reset functions to return a warning instead of a value.
- Utilize devm_reset_control_get_optional to prevent failure when
reset_control is missing.
- Use 'true' and 'false' for boolean values.
- Remove the CONFIG_RESET_CONTROLLER check as stub methods are sufficient
when undefined.
Powered by blists - more mailing lists