Now arch code has to specify CONFIG_ARCH_HAS_BANDGAP. So, this driver
will be selectable only if the platform reports itself as having a
bandgap device.
Any OMAP variant or any other OMAP version needs to
select ARCH_HAS_BANDGAP
so that the driver will be applicable. A part from that it is
required to device the data structures that maps the registers
and their bitfields. The DT compatible list must also be updated.
CC: Santosh Shilimkar <[email protected]>
CC: Vaibhav Bedia <[email protected]>
Signed-off-by: Eduardo Valentin <[email protected]>
---
drivers/staging/omap-thermal/Kconfig | 2 +-
drivers/staging/omap-thermal/TODO | 1 -
2 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/omap-thermal/Kconfig
b/drivers/staging/omap-thermal/Kconfig
index 30cbc3b..52170bf 100644
--- a/drivers/staging/omap-thermal/Kconfig
+++ b/drivers/staging/omap-thermal/Kconfig
@@ -1,7 +1,7 @@
config OMAP_BANDGAP
tristate "Texas Instruments OMAP4+ temperature sensor driver"
depends on THERMAL
- depends on ARCH_OMAP4 || SOC_OMAP5
+ depends on ARCH_HAS_BANDGAP
help
If you say yes here you get support for the Texas Instruments
OMAP4460+ on die bandgap temperature sensor support. The register
diff --git a/drivers/staging/omap-thermal/TODO
b/drivers/staging/omap-thermal/TODO
index 9e23cc4..77b761b 100644
--- a/drivers/staging/omap-thermal/TODO
+++ b/drivers/staging/omap-thermal/TODO
@@ -20,7 +20,6 @@ on omap5-thermal.c
- Add support for GPU cooling
generally:
-- write Kconfig dependencies so that omap variants are covered
- make checkpatch.pl and sparse happy
- make sure this code works on OMAP4430, OMAP4460 and OMAP5430
- update documentation
--
1.7.7.1.488.ge8e1c
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
