diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2022-04-28 10:39:34 +0300 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2022-04-28 10:39:34 +0300 |
| commit | be5fd933f8c15967931121aa8a0e521bf2802e71 (patch) | |
| tree | 71b7fb9997910ed9b2e90a94fdd0a2e5e6d7dd14 /net/bpf | |
| parent | 50c6afabfd2ae91a4ff0e2feb14fe702b0688ec5 (diff) | |
| parent | a8db203db05c5271e59647adc0855c7290455a35 (diff) | |
| download | linux-be5fd933f8c15967931121aa8a0e521bf2802e71.tar.xz | |
Merge branch 'add-reset-deassertion-for-aspeed-mdio'
Dylan Hung says:
====================
Add reset deassertion for Aspeed MDIO
Add missing reset deassertion for Aspeed MDIO bus controller. The reset
is asserted by the hardware when power-on so the driver only needs to
deassert it. To be able to work with the old DT blobs, the reset is
optional since it may be deasserted by the bootloader or the previous
kernel.
V6:
- fix merge conflict for net-next
V5:
- fix error of dt_binding_check
V4:
- use ASPEED_RESET_MII instead of hardcoding in dt-binding example
V3:
- remove reset property from the required list of the device tree
bindings
- remove "Cc: stable@vger.kernel.org" from the commit messages
- add more description in the commit message of the dt-binding
V2:
- add reset property in the device tree bindings
- add reset assertion in the error path and driver remove
====================
Link: https://lore.kernel.org/r/20220427035501.17500-1-dylan_hung@aspeedtech.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'net/bpf')
0 files changed, 0 insertions, 0 deletions