I think I need some more context to understand this diff.

Bump to latest v1.8.1 and bump fu540 u-boot revision

In D54421#1243662, @lwhsu wrote:

I think the question is more "do we want to support FU540?"

If the workaround is still working and no impact to others, it probably doesn't very hurt.
But it it cause issues, we may remove its support, along with sysutils/u-boot-sifive-fu540.

In D51076#1237849, @ziaee wrote:

Why abandon?

In D37981#1213421, @markj wrote:

In D37981#1210335, @avg wrote:

Totally belated, but would it make (have made) sense to split default behavior of reboot and reset commands?
I think that it would be more natural if reboot tried to do a reboot and reset just went for a reset (where implemented)?

I think that would make sense. In retrospect it's a bit silly that reboot and reset are aliases of each other, and both have the /s modifier.

Most likely, this same treatment should be applied to the similar cd_detect() function in sys/dev/sdhci/sdhci_fdt_gpio.c.

@imp any objection?

I have not succeeded in using this myself, but I have never tried too hard.

Committed. Forgot the DR tag.

Yes, please go ahead!

In D53119#1213368, @jrtc27 wrote:

The logic for removing this in the FDT is that, on Linux, the clock framework comes up early enough (or at least some early part of it) in order to be able to query the UART clock's frequency from the clock driver, whereas we don't do anything like that with clocks prior to newbus passes, so way too late for cninit.