Skip to contentSkip to conversation

arm64: enable ARCH_HAS_BANDGAP config

PATCH New Abhilash Kesavan 4 participants 6 messages Nov 14, 2014 – Dec 2, 2014 arm64

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---
 arch/arm64/Kconfig |    3 +++
 1 file changed, 3 insertions(+)
arch/arm64/Kconfig +3 -0
index 5bb1900..7c452e4 100644
@@ -139,6 +139,9 @@ config KERNEL_MODE_NEON
 config FIX_EARLYCON_MEM
 	def_bool y
 
+config ARCH_HAS_BANDGAP
+	def_bool y
+
 source "init/Kconfig"
 
 source "kernel/Kconfig.freezer"
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

Hi Abhilash,

Quoted 6 lines · Abhilash Kesavan

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---

HAS_BANDGAP was added to ARM to indicate that arch supports a bandgap device like a thermal management unit, so this looks good to me.

Quoted 25 lines
 arch/arm64/Kconfig |    3 +++
 1 file changed, 3 insertions(+)
arch/arm64/Kconfig +3 -1
index 5bb1900..7c452e4 100644
@@ -139,6 +139,9 @@ config KERNEL_MODE_NEON
 config FIX_EARLYCON_MEM
        def_bool y
 
+config ARCH_HAS_BANDGAP
+       def_bool y
+
 source "init/Kconfig"
 
 source "kernel/Kconfig.freezer"
--

1.7.9.5

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Signature · 2 lines
Regards,
Alim
maintainer
#2 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

Quoted 9 lines · Alim Akhtar
Quoted 6 lines · Abhilash Kesavan

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---

HAS_BANDGAP was added to ARM to indicate that arch supports a bandgap device like a thermal management unit, so this looks good to me.

But it doesn't look good to me. ARCH_HAS_* kind of implies that the architecture has some feature or the port provides some feature. But in the current use, it simply allows the enabling of the menu config entries for two drivers (EXYNOS_THERMAL and TI_SOC_THERMAL).

If you want to specify that the SoC has a device, just use DT and not some random config option that only enables the menu entry for the corresponding driver.

Signature · 1 line
Catalin
#3 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

Hi Catalin,

Quoted 11 lines · Catalin Marinas
Quoted 9 lines · Alim Akhtar
Quoted 6 lines · Abhilash Kesavan

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---

HAS_BANDGAP was added to ARM to indicate that arch supports a bandgap device like a thermal management unit, so this looks good to me.

Quoted 8 lines

But it doesn't look good to me. ARCH_HAS_* kind of implies that the architecture has some feature or the port provides some feature. But in the current use, it simply allows the enabling of the menu config entries for two drivers (EXYNOS_THERMAL and TI_SOC_THERMAL).

If you want to specify that the SoC has a device, just use DT and not some random config option that only enables the menu entry for the corresponding driver.

So, you are suggesting that the ARCH_HAS_BANDGAP dependency for these two drivers be removed ? I am not aware of the history behind adding this symbol, but as it is only used by the 2 platforms it should be easy to remove.

Regards,
Abhilash

Quoted 3 lines

--
Catalin

maintainer
#4 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

Quoted 18 lines · Abhilash Kesavan
Quoted 16 lines · Catalin Marinas
Quoted 9 lines · Alim Akhtar
Quoted 6 lines · Abhilash Kesavan

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---

HAS_BANDGAP was added to ARM to indicate that arch supports a bandgap device like a thermal management unit, so this looks good to me.

But it doesn't look good to me. ARCH_HAS_* kind of implies that the architecture has some feature or the port provides some feature. But in the current use, it simply allows the enabling of the menu config entries for two drivers (EXYNOS_THERMAL and TI_SOC_THERMAL).

Quoted 8 lines
Quoted 3 lines

If you want to specify that the SoC has a device, just use DT and not some random config option that only enables the menu entry for the corresponding driver.

So, you are suggesting that the ARCH_HAS_BANDGAP dependency for these two drivers be removed ? I am not aware of the history behind adding this symbol, but as it is only used by the 2 platforms it should be easy to remove.

Yes. You have defconfig for those platforms anyway. If you only want to enable a driver for a certain SoC, put a dependency on that SoC config (it doesn't look like some generic driver that is used by multiple SoCs).

Signature · 1 line
Catalin
#5 lore raw

PATCH 1/1 arm64: enable ARCH_HAS_BANDGAP config

In reply to Catalin Marinas

Hi Catalin,

Quoted 11 lines · Catalin Marinas
Quoted 9 lines · Alim Akhtar
Quoted 6 lines · Abhilash Kesavan

Some of the existing thermal drivers (ti and exynos) have a dependency on ARCH_HAS_BANDGAP. Activate ARCH_HAS_BANDGAP config entry for ARM64 so that these drivers may be re-used.

---

HAS_BANDGAP was added to ARM to indicate that arch supports a bandgap device like a thermal management unit, so this looks good to me.

Quoted 9 lines

But it doesn't look good to me. ARCH_HAS_* kind of implies that the architecture has some feature or the port provides some feature. But in the current use, it simply allows the enabling of the menu config entries for two drivers (EXYNOS_THERMAL and TI_SOC_THERMAL).

If you want to specify that the SoC has a device, just use DT and not some random config option that only enables the menu entry for the corresponding driver.

Well completely agree with you.
Not sure why this was done for ARM though.

Quoted 2 lines

--
Catalin

Signature · 2 lines
Regards,
Alim