On Sat, Mar 3, 2018 at 8:56 AM, Andy Shevchenko <andy.shevchenko@xxxxxxxxx> wrote: > On Fri, Mar 2, 2018 at 8:35 PM, Daniel Kurtz <djkurtz@xxxxxxxxxxxx> wrote: >> On Thu, Mar 1, 2018 at 1:02 PM Andy Shevchenko <andy.shevchenko@xxxxxxxxx> >> wrote: >>> On Thu, Mar 1, 2018 at 9:22 PM, Daniel Kurtz <djkurtz@xxxxxxxxxxxx> wrote: >>> > On Thu, Mar 1, 2018 at 11:47 AM Andy Shevchenko < >> andy.shevchenko@xxxxxxxxx> >>> > wrote: > >> the UART bitclock >> is >>> > always "BASE_BAUD * 16" (1843200). While this may be true for many >> UARTs, >>> > it isn't true for AMD's CZ/ST which has a 8250_dw and uses a fixed 48 >> MHz >>> > clock. The main 8250_dw driver uses devm_clk_get to get the "baudclk" >> and >>> > uses its rate to initialize uartclk. For AMD CZ/ST, this "baudclk" is >>> > actually a set up in acpi_apd.c when there is an acpi match for >> "AMD0020", >>> > with a rate read from the .fixed_clk_rate param of the corresponding >>> > apd_device_desc. > >> As >>> > noted above, the information is actually already in the kernel and used >> by >>> > 8250_dw - I would happy be to hear recommendations for wiring this data >>> > into earlycon that doesn't require adding another command line arg. > > Brief look at the code shows that ->setup() call back is executed > after setting initial (which is hardcoded) clock. > > What you need is to either create another type of earlycon for your > device with accompanied ->setup() callback, or patch 8250_early.c. If I'm understand you correctly, you are suggesting new driver code that sets the clock accordingly within the port structure such that the baud rate calculation actually works based on the correct input clock? Why wouldn't we just extened the generic earlycon driver like the original patch to support providing the clock? Anything in the earlycon path that tries to set a baud rate will fail once the hard-coded input clock assumption doesn't hold true. Why not provide the ability to correct the assumption for platforms that need it? > >>> > I see that support was also added recently to earlycon to let it use >> ACPI >>> > SPCR to choose a console and configure its parameters... but AFAICT, >> this >>> > path also doesn't allow specifying the uart clock. > > It does specify baudrate. It means it's _firmware_ responsibility to > configure UART device properly. baudrate != input clock. The issue is that once the driver code attempts to set a baud rate w/o having the correct input clock then things break. > >>> Fix your firmware then. It should set console to 115200 like (almost) >>> everyone does. >>> Okay, configures a necessary IPs to feed UART with expected 1.8432M clock. >> >> The console is 115200 when it is enabled. However, the firmware does not >> always enable it by default. > > Another firmware bug. It's more complex than that. You seem to take the stance that the firmware should bring every IP block out of reset and/or clock and power gating. That then subsequently requires the kernel to enable all those soc drivers that put those devices in power or clock gated state to reach the maximum power savings. While that's certainly possible, it just leads to bloated kernels. That is orthogonal to the problem of setting baud rate w/o knowing the proper input clock frequency, though. If we do make the assumption the firmware sets up the uart, but the kernel earlycon has a different baud rate specified than what firmware set up then the baud rate calculation would be wrong as well since the input clock isn't known. As such one cannot use earlycon when: 1. firmware doesn't set up uart 2. firmware baud rate != earlycon specified baud rate. Providing the proper input clock for the device in question solves both 1 and 2. > >> The problem is that the UART IP block has a fixed 48 MHz input clock, but >> earlycon assumes this clock is always 1843200. > >> I looked a bit further, and I think this patch (or something similar) is >> still required to teach generic earlycon how to handle an explicit >> port->uartclk (ie, one that is not 1843200). >> The extended string can then be explicitly set on the kernel command line >> for this kind of hardware. > > No. > >> In addition, we can add another patch with a new quirk detector in >> drivers/acpi/spcr.c:acpi_parse_spcr() to handle this hardware. >> acpi_parse_spcr() can then use the extended option string to pass in the >> appropriate UART clock to setup_eralycon(). > > Definitely no. It's not defined in SPCR spec. > >> This would again allow a user to just use the simple command line parameter >> "earlycon" if the device's firmware has a correctly confiured ACPI SPCR >> table. > > NAK to the patch, see above alternatives. > > -- > With Best Regards, > Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
