On 12/13/2016 01:20 AM, Jon Masters wrote: > On 12/07/2016 10:23 AM, Mark Salter wrote: >> If you specify a baudrate with earlycon=, the driver tries to set that >> baudrate and if you have an 8250 with some non-standard baud clock, then >> it will fail. Perhaps SPCR shouldn't pass baud option to setup_earlycon(). > > Yet they seem to explicitly want to do this...in my conversations with some > others we agree that, in many cases, you really want to say "leave the baud > whatever the firmware set it", which would work in this case, but might > break some others. Then again, nobody on x86 Linux is really using the > SPCR today due to it not having been something they used until now and > due to the location of the COM ports being fairly well known ;) > > So who knows what folks will prefer, but we should at least get the spec > to cover both situations by explicitly calling out Applied as special. <snip> > So I've been discussing some changes to the SPCR and the current proposal > is that we have two new subtypes - one for 16550s that are non-standard > register width/stride but use the typical base clock, and a specific > additional type for SBSA level 0 compatible 16550 UARTs (Applied). I > will followup when the specification document has been revised. As an update. I've been speaking with friends at Microsoft on and off about this for quite some time. They've been very helpful (as usual) and we should get an SPCR update soon covering Applied's case. I have pinged the APM team to make sure that they're ready to post a patch. I would like this small fix squeezed in 4.12, but before 4.13. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
