Re: [PATCH v2 13/13] arm64: defconfig: Enable I3C and SPD5118 hwmon
Guenter Roeck <[email protected]>
| Newsgroups | dev.linux.lists.acpica-devel,org.infradead.lists.linux-i3c,org.kernel.vger.linux-acpi,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-hwmon,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 4/10/26 22:34, Akhil R wrote: [ ... ] >>>> And it >>>> should bring me clear rule what I can or cannot remove from defconfig, >>>> if in 2 years I come and start pruning it from symbols. > > I am still a little confused on what information would likely accept (and > keep) these configs in the defconfig. Would updating the commit message > as below work? > > "These configs enable the support for SPD5118 within the > Small-Outline-Compression-Attached Memory Modules (SOCAMM) LPDDR5X found > in the NVIDIA Vera CPUs. The Vera CPU uses ACPI and is part of platforms > such as Vera Rubin." > It is quite interesting that we argue about SPD5118 which is mandatory in DDR5 systems. At the same time, CONFIG_IGB_HWMON, CONFIG_SENSORS_MACSMC_HWMON, CONFIG_SENSORS_RASPBERRYPI_HWMON, and CONFIG_RTC_DRV_DS3232_HWMON _are_ enabled in arm64:defconfig. CONFIG_IGB_HWMON is even built-in. It is kind of difficult to understand why those are more important than the temperature sensor on DDR5 modules (or the temperature sensor on DDR4 modules, for that matter). I don't know what the policy for defconfig is, but just based on that it does seem to lack consistency. A separate question is if it is time to enable I3C in default configurations. I'd think so - more and more chip vendors support it, and presumably they would not invest in it if there was no demand, but that is just my personal opinion. Guenter