FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-11-17T14:59:58Z 2020-11-17T14:59:58Z Emmanuel Vadot manu@FreeBSD.org 2020-11-17T14:59:58Z urn:sha1:e35c28a24b850afd23beccf9c6683d9cd0b7c4b3 This allow to get a syscon node defined under a specific fdt node (which isn't always the device one). 2020-10-17T23:42:33Z Bjoern A. Zeeb bz@FreeBSD.org 2020-10-17T23:42:33Z urn:sha1:3d8a0ab61da10c861e90c7b3029c006bbfd3dbe1 Just fix indentation of an if() clause. No functional changes intended. MFC after: 3 days 2020-10-01T09:50:08Z Michal Meloun mmel@FreeBSD.org 2020-10-01T09:50:08Z urn:sha1:c19440e3502be65a84af0c56fbcd48898e4325f8 Mutex should be owned in affected functions. Reborted by: emaste MFC after: 4 weeks MFC with: r366161 2020-09-25T16:44:01Z Michal Meloun mmel@FreeBSD.org 2020-09-25T16:44:01Z urn:sha1:01d0f9c0e40a44cff5e25842b72075cbaf0864de In some cases, the syscon driver may be used by consumer requiring better control about locking (ie. it may be used as registe file provider for clock driver which needs locked access to multiple registers). Add fine locking protocol methods together with bunch of helper functions in syscon driver and implement this functionality in syscon_generic driver. MFC after: 4 weeks 2020-09-25T13:52:31Z Michal Meloun mmel@FreeBSD.org 2020-09-25T13:52:31Z urn:sha1:8dc348a47965722ce5302636f1262d8516fba2c3 Syscon can also have child nodes that share a registration file with it. To do this correctly, follow these steps: - subclass syscon from simplebus and expose it if the node is also "simple-bus" compatible. - block simplebus probe for this compatible string, so it's priority (bus pass) doesn't colide with syscon driver. While I'm in, also block "syscon", "simple-mfd" for the same reason. MFC after: 4 weeks 2020-09-07T06:27:18Z Andriy Gapon avg@FreeBSD.org 2020-09-07T06:27:18Z urn:sha1:c3a7328be8b3269c49e3aa1fe29783f0c21d1e55 abs() takes a (signed) int as input. Instead, it was used with unsigned 64-bit integers. So, add and use a new helper function to calculate a difference between two uint64_t-s. Reviewed by: manu MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D26307 2020-07-26T18:19:50Z Jessica Clarke jrtc27@FreeBSD.org 2020-07-26T18:19:50Z urn:sha1:28da7c9ed0f28f79a819b4003b32e81a3fdf55b5 This device driver supports both syscon-power and syscon-reset devices, as specified in [1] and [2]. These provide a very simple interface for power and reset control, and among other things are used by QEMU's virt machine on RISC-V. A separate commit will enable this on RISC-V, as that requires adding a RISC-V-specific riscv_syscon akin to r327936's aw_syscon. [1] https://www.kernel.org/doc/Documentation/devicetree/bindings/power/reset/syscon-poweroff.txt [2] https://www.kernel.org/doc/Documentation/devicetree/bindings/power/reset/syscon-reboot.txt Reviewed by: brooks (mentor), jhb (mentor) Approved by: brooks (mentor), jhb (mentor) Obtained from: CheriBSD Differential Revision: https://reviews.freebsd.org/D25724 2020-07-25T06:32:23Z Michal Meloun mmel@FreeBSD.org 2020-07-25T06:32:23Z urn:sha1:d873a521cad3dfa744d069c9a682c6ac0d21d837 As Emanuel poited me the Linux processes these clock assignments in forward order, not in reversed. I misread the original code. Tha problem with wrong order for assigned clocks found in tegra (and some imx) DT should be reanalyzed and solved by different way. MFC with: r363123 Reported by; manu 2020-07-12T07:59:15Z Michal Meloun mmel@FreeBSD.org 2020-07-12T07:59:15Z urn:sha1:c0c5cf7b31ff943dc4f0d473f9b03efb1c6d6fba Linux processes these clocks in reverse order and some DT relies on this fact. For example, the frequency setting for a given PLL is the last in the list, preceded by the frequency setting of its following divider or so... MFC after: 1 week 2020-07-12T07:42:21Z Michal Meloun mmel@FreeBSD.org 2020-07-12T07:42:21Z urn:sha1:a9be5d7515f96cfce750984e21458e11e9d755a7 MFC after: 1 week