lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2014 12:46:17 +0200
From:	Arnd Bergmann <>
To:	Graeme Gregory <>
	Olof Johansson <>,
	Hanjun Guo <>,
	Mark Rutland <>,
	Mark Brown <>,
	Catalin Marinas <>,
	Will Deacon <>,
	Lv Zheng <>,
	Lorenzo Pieralisi <>,
	Daniel Lezcano <>,
	Robert Moore <>,
	"" <>,
	Grant Likely <>,
	Charles Garcia-Tobin <>,
	Robert Richter <>,
	Jason Cooper <>,
	Marc Zyngier <>,
	Liviu Dudau <>,
	Bjorn Helgaas <>,
	Randy Dunlap <>,
	"Rafael J. Wysocki" <>,
	"" <>,
	Sudeep Holla <>
Subject: Re: [PATCH 19/19] Documentation: ACPI for ARM64

On Monday 28 July 2014 10:23:57 Graeme Gregory wrote:
> The PL011 UART is the use-case I keep hitting, that IP block has a 
> variable input clock on pretty much everything I have seen in the wild. 

Ok, I see. What does ACPI-5.1 say about pl011?

Interestingly, the subset of pl011 that is specified by SBSA does not
contain the IBRD/FBRD registers, effectively making it a fixed-rated
UART (I guess that would be a ART, without the U then), and you
consequently don't even need to know the clock rate.

However, my guess is that most hardware in the real world contains
an actual pl011 and it does make a lot of sense to allow setting
the baud rate on it, which then requires knowing the input clock.

If there is any hardware that implements just the SBSA-mandated subset
rather than the full pl011, we should probably implement both
in the kernel: a dumb driver that can only send and receive, and the
more complex one that can set the bit rates and flow-control but that
requires a standardized ACPI table with the input clock rate.

Whether the two would belong into one file or two separate driver
modules is something I can't tell, it would be up to the serial
maintainers to decide.

> I really hope that this use does not spread beyond a few essential 
> devices like the UART. IMO all real hardware should be the other side of 
> a PCIe bridge.

I would definitely agree with that.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists