mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
38c23685b2
The main addition this time around is the new ARM "SCMI" framework, which is the latest in a series of standards coming from ARM to do power management in a platform independent way. This has been through many review cycles, and it relies on a rather interesting way of using the mailbox subsystem, but in the end I agreed that Sudeep's version was the best we could do after all. Other changes include: - the ARM CCN driver is moved out of drivers/bus into drivers/perf, which makes more sense. Similarly, the performance monitoring portion of the CCI driver are moved the same way and cleaned up a little more. - a series of updates to the SCPI framework - support for the Mediatek mt7623a SoC in drivers/soc - support for additional NVIDIA Tegra hardware in drivers/soc - a new reset driver for Socionext Uniphier - lesser bug fixes in drivers/soc, drivers/tee, drivers/memory, and drivers/firmware and drivers/reset across platforms -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJaxiNzAAoJEGCrR//JCVInYhYP/2kPhc5t/kszA1bcklcbO9dY eX37Ra/RR4yQ5yeQZVIZ4UkUovxk9PmG2tM4K5oJaTDsz5pPEgavVOOr3sbfj6vb 4O9auTeysEQlHcbVdNFum0YS2gUY2YD7D12DTRorotLxCqod184ccWXq0XGfIWaY l3YRrcL/lPlqmyS3z/GNx9oNygOMUzEfXfIQYICyzHuYiLBUGnkKC1vIb+Hx1TDq Cxk++AUqH13Mss24O2A2QQh+oBHj2BybDLLqwcC5PSpsUbFrVCfzG54l43mig32T NOxV0Qnml2wAtU4H0QcgtSgwRimHD0YOiX8ssquvDDiqTqM5G+llSTGkEbYe+AUW 4GIZYoBOwGkfEXS+tyymHe9yfc5h1OLYAeFU1jRm723c7phanuu67rPn35YC8UMK zSql10JpkAGNzMikrxxb6wnis951w2UFlzhgZQ6ItA/nRq3l+oEQA0Qiljv965nz DVLsD5+gdhK6GBctkzlsD5HFn6GjM8JilnsOVPHD765nKnVBSxKiXRLV228XVug2 rChF1FhQqLnM54jCMqHZX5fS9SbSgtYswHqIXpVw6GmJkqq/Ly10yGR0vuWD+uyn BV7q5AKpGrwm6wZkMM2uZ1VdUtWzn856AbkqrvX/QhmJcX4McuqaLUrC8bSOj1ty KeVil0akq3nU+xHl5Ojs =Pmsx -----END PGP SIGNATURE----- Merge tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc Pull ARM SoC driver updates from Arnd Bergmann: "The main addition this time around is the new ARM "SCMI" framework, which is the latest in a series of standards coming from ARM to do power management in a platform independent way. This has been through many review cycles, and it relies on a rather interesting way of using the mailbox subsystem, but in the end I agreed that Sudeep's version was the best we could do after all. Other changes include: - the ARM CCN driver is moved out of drivers/bus into drivers/perf, which makes more sense. Similarly, the performance monitoring portion of the CCI driver are moved the same way and cleaned up a little more. - a series of updates to the SCPI framework - support for the Mediatek mt7623a SoC in drivers/soc - support for additional NVIDIA Tegra hardware in drivers/soc - a new reset driver for Socionext Uniphier - lesser bug fixes in drivers/soc, drivers/tee, drivers/memory, and drivers/firmware and drivers/reset across platforms" * tag 'armsoc-drivers' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc: (87 commits) reset: uniphier: add ethernet reset control support for PXs3 reset: stm32mp1: Enable stm32mp1 reset driver dt-bindings: reset: add STM32MP1 resets reset: uniphier: add Pro4/Pro5/PXs2 audio systems reset control reset: imx7: add 'depends on HAS_IOMEM' to fix unmet dependency reset: modify the way reset lookup works for board files reset: add support for non-DT systems clk: scmi: use devm_of_clk_add_hw_provider() API and drop scmi_clocks_remove firmware: arm_scmi: prevent accessing rate_discrete uninitialized hwmon: (scmi) return -EINVAL when sensor information is unavailable amlogic: meson-gx-socinfo: Update soc ids soc/tegra: pmc: Use the new reset APIs to manage reset controllers soc: mediatek: update power domain data of MT2712 dt-bindings: soc: update MT2712 power dt-bindings cpufreq: scmi: add thermal dependency soc: mediatek: fix the mistaken pointer accessed when subdomains are added soc: mediatek: add SCPSYS power domain driver for MediaTek MT7623A SoC soc: mediatek: avoid hardcoded value with bus_prot_mask dt-bindings: soc: add header files required for MT7623A SCPSYS dt-binding dt-bindings: soc: add SCPSYS binding for MT7623 and MT7623A SoC ...
200 lines
5.9 KiB
Plaintext
200 lines
5.9 KiB
Plaintext
======================================================================
|
|
Device tree bindings for the Aspeed Low Pin Count (LPC) Bus Controller
|
|
======================================================================
|
|
|
|
The LPC bus is a means to bridge a host CPU to a number of low-bandwidth
|
|
peripheral devices, replacing the use of the ISA bus in the age of PCI[0]. The
|
|
primary use case of the Aspeed LPC controller is as a slave on the bus
|
|
(typically in a Baseboard Management Controller SoC), but under certain
|
|
conditions it can also take the role of bus master.
|
|
|
|
The LPC controller is represented as a multi-function device to account for the
|
|
mix of functionality it provides. The principle split is between the register
|
|
layout at the start of the I/O space which is, to quote the Aspeed datasheet,
|
|
"basically compatible with the [LPC registers from the] popular BMC controller
|
|
H8S/2168[1]", and everything else, where everything else is an eclectic
|
|
collection of functions with a esoteric register layout. "Everything else",
|
|
here labeled the "host" portion of the controller, includes, but is not limited
|
|
to:
|
|
|
|
* An IPMI Block Transfer[2] Controller
|
|
|
|
* An LPC Host Controller: Manages LPC functions such as host vs slave mode, the
|
|
physical properties of some LPC pins, configuration of serial IRQs, and
|
|
APB-to-LPC bridging amonst other functions.
|
|
|
|
* An LPC Host Interface Controller: Manages functions exposed to the host such
|
|
as LPC firmware hub cycles, configuration of the LPC-to-AHB mapping, UART
|
|
management and bus snoop configuration.
|
|
|
|
* A set of SuperIO[3] scratch registers: Enables implementation of e.g. custom
|
|
hardware management protocols for handover between the host and baseboard
|
|
management controller.
|
|
|
|
Additionally the state of the LPC controller influences the pinmux
|
|
configuration, therefore the host portion of the controller is exposed as a
|
|
syscon as a means to arbitrate access.
|
|
|
|
[0] http://www.intel.com/design/chipsets/industry/25128901.pdf
|
|
[1] https://www.renesas.com/en-sg/doc/products/mpumcu/001/rej09b0078_h8s2168.pdf?key=7c88837454702128622bee53acbda8f4
|
|
[2] http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/ipmi-second-gen-interface-spec-v2-rev1-1.pdf
|
|
[3] https://en.wikipedia.org/wiki/Super_I/O
|
|
|
|
Required properties
|
|
===================
|
|
|
|
- compatible: One of:
|
|
"aspeed,ast2400-lpc", "simple-mfd"
|
|
"aspeed,ast2500-lpc", "simple-mfd"
|
|
|
|
- reg: contains the physical address and length values of the Aspeed
|
|
LPC memory region.
|
|
|
|
- #address-cells: <1>
|
|
- #size-cells: <1>
|
|
- ranges: Maps 0 to the physical address and length of the LPC memory
|
|
region
|
|
|
|
Required LPC Child nodes
|
|
========================
|
|
|
|
BMC Node
|
|
--------
|
|
|
|
- compatible: One of:
|
|
"aspeed,ast2400-lpc-bmc"
|
|
"aspeed,ast2500-lpc-bmc"
|
|
|
|
- reg: contains the physical address and length values of the
|
|
H8S/2168-compatible LPC controller memory region
|
|
|
|
Host Node
|
|
---------
|
|
|
|
- compatible: One of:
|
|
"aspeed,ast2400-lpc-host", "simple-mfd", "syscon"
|
|
"aspeed,ast2500-lpc-host", "simple-mfd", "syscon"
|
|
|
|
- reg: contains the address and length values of the host-related
|
|
register space for the Aspeed LPC controller
|
|
|
|
- #address-cells: <1>
|
|
- #size-cells: <1>
|
|
- ranges: Maps 0 to the address and length of the host-related LPC memory
|
|
region
|
|
|
|
Example:
|
|
|
|
lpc: lpc@1e789000 {
|
|
compatible = "aspeed,ast2500-lpc", "simple-mfd";
|
|
reg = <0x1e789000 0x1000>;
|
|
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
ranges = <0x0 0x1e789000 0x1000>;
|
|
|
|
lpc_bmc: lpc-bmc@0 {
|
|
compatible = "aspeed,ast2500-lpc-bmc";
|
|
reg = <0x0 0x80>;
|
|
};
|
|
|
|
lpc_host: lpc-host@80 {
|
|
compatible = "aspeed,ast2500-lpc-host", "simple-mfd", "syscon";
|
|
reg = <0x80 0x1e0>;
|
|
reg-io-width = <4>;
|
|
|
|
#address-cells = <1>;
|
|
#size-cells = <1>;
|
|
ranges = <0x0 0x80 0x1e0>;
|
|
};
|
|
};
|
|
|
|
BMC Node Children
|
|
==================
|
|
|
|
|
|
Host Node Children
|
|
==================
|
|
|
|
LPC Host Interface Controller
|
|
-------------------
|
|
|
|
The LPC Host Interface Controller manages functions exposed to the host such as
|
|
LPC firmware hub cycles, configuration of the LPC-to-AHB mapping, UART
|
|
management and bus snoop configuration.
|
|
|
|
Required properties:
|
|
|
|
- compatible: One of:
|
|
"aspeed,ast2400-lpc-ctrl";
|
|
"aspeed,ast2500-lpc-ctrl";
|
|
|
|
- reg: contains offset/length values of the host interface controller
|
|
memory regions
|
|
|
|
- clocks: contains a phandle to the syscon node describing the clocks.
|
|
There should then be one cell representing the clock to use
|
|
|
|
- memory-region: A phandle to a reserved_memory region to be used for the LPC
|
|
to AHB mapping
|
|
|
|
- flash: A phandle to the SPI flash controller containing the flash to
|
|
be exposed over the LPC to AHB mapping
|
|
|
|
Example:
|
|
|
|
lpc-host@80 {
|
|
lpc_ctrl: lpc-ctrl@0 {
|
|
compatible = "aspeed,ast2500-lpc-ctrl";
|
|
reg = <0x0 0x80>;
|
|
clocks = <&syscon ASPEED_CLK_GATE_LCLK>;
|
|
memory-region = <&flash_memory>;
|
|
flash = <&spi>;
|
|
};
|
|
};
|
|
|
|
LPC Host Controller
|
|
-------------------
|
|
|
|
The Aspeed LPC Host Controller configures the Low Pin Count (LPC) bus behaviour
|
|
between the host and the baseboard management controller. The registers exist
|
|
in the "host" portion of the Aspeed LPC controller, which must be the parent of
|
|
the LPC host controller node.
|
|
|
|
Required properties:
|
|
|
|
- compatible: One of:
|
|
"aspeed,ast2400-lhc";
|
|
"aspeed,ast2500-lhc";
|
|
|
|
- reg: contains offset/length values of the LHC memory regions. In the
|
|
AST2400 and AST2500 there are two regions.
|
|
|
|
Example:
|
|
|
|
lhc: lhc@20 {
|
|
compatible = "aspeed,ast2500-lhc";
|
|
reg = <0x20 0x24 0x48 0x8>;
|
|
};
|
|
|
|
LPC reset control
|
|
-----------------
|
|
|
|
The UARTs present in the ASPEED SoC can have their resets tied to the reset
|
|
state of the LPC bus. Some systems may chose to modify this configuration.
|
|
|
|
Required properties:
|
|
|
|
- compatible: "aspeed,ast2500-lpc-reset" or
|
|
"aspeed,ast2400-lpc-reset"
|
|
- reg: offset and length of the IP in the LHC memory region
|
|
- #reset-controller indicates the number of reset cells expected
|
|
|
|
Example:
|
|
|
|
lpc_reset: reset-controller@18 {
|
|
compatible = "aspeed,ast2500-lpc-reset";
|
|
reg = <0x18 0x4>;
|
|
#reset-cells = <1>;
|
|
};
|