[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sun, 3 Mar 2019 10:49:24 +0200
From: Talel Shenhar <talel@...zon.com>
To: <edubezval@...il.com>, <rui.zhang@...el.com>,
<linux-kernel@...r.kernel.org>, <linux-pm@...r.kernel.org>,
<robh+dt@...nel.org>, <mark.rutland@....com>,
<devicetree@...r.kernel.org>, <talel@...zon.com>,
<hhhawa@...zon.com>, <jonnyc@...zon.com>, <ronenk@...zon.com>,
<hanochu@...zon.com>
Subject: [PATCH 0/2] Thermal MMIO Driver
This series introduces the generic thermal MMIO driver that will use
memory mapped reads to get the temperature. Any HW/System that
allows temperature reading by a single memory-mapped reading, be it
register or shared memory, is a potential candidate to work with this
driver.
This driver is most suitable for cases such as the following:
- The entire thermal HW setup is done by another SW entity (e.g.
bootloader) and all that is left is to read the current temperature from
a register.
- The thermal HW setup is done via an external CPU (e.g. micro-controller)
and that CPU has is using shared memory that can be memory-mapped to this
driver.
- The thermal HW setup and reading is done via CPLD, which exports the
current temperature to the system via a register.
- The thermal HW is working out-of-the-box and only reports temperature via
a single register access.
Talel Shenhar (2):
dt-bindings: thermal: thermal_mmio: Add binding documentation
thermal: Introduce thermal MMIO
.../devicetree/bindings/thermal/thermal_mmio.txt | 173 +++++++++++++++++
drivers/thermal/Kconfig | 11 ++
drivers/thermal/Makefile | 3 +
drivers/thermal/thermal_mmio.c | 214 +++++++++++++++++++++
4 files changed, 401 insertions(+)
create mode 100644 Documentation/devicetree/bindings/thermal/thermal_mmio.txt
create mode 100644 drivers/thermal/thermal_mmio.c
--
2.7.4
Powered by blists - more mailing lists