Rename prefixed config filesNow that these files are all in folders, we don't need to prefix thenames. Not all folders ended up following the companyname_<model>pattern, so fix the ones that nee
Rename prefixed config filesNow that these files are all in folders, we don't need to prefix thenames. Not all folders ended up following the companyname_<model>pattern, so fix the ones that need fixed.Open to suggestion if there's a better pattern we should follow, butportions of the repo already follow this pattern, so we should beconsistent.Change-Id: Ieb27b7c894f43db90fcf40709befc79aa9f3bcbfSigned-off-by: Ed Tanous <etanous@nvidia.com>
show more ...
configurations: Align humidity sensor names with dbus-sensors changesThis patch updates sensor configuration files to reflect the correctedsensor naming scheme for multi-function sensors such as B
configurations: Align humidity sensor names with dbus-sensors changesThis patch updates sensor configuration files to reflect the correctedsensor naming scheme for multi-function sensors such as BME280. Thischange ensures consistency with the naming conventions defined in`HwmonTempMain.cpp` and aligns with recent updates in the `dbus-sensors`repository.Previously, both pressure and humidity readings used the same key("Name1"), which led to confusion and potential misinterpretation ofsensor data.This patch replaces sensor naming keys as follows: - "Name1" → "NamePressure" - "Name2" → "NameHumidity"This change ensures proper mapping and indexing of humidity and pressuresensors on D-Bus, preventing conflicts and improving the reliability ofsensor readings. It directly addresses the changes introduced in:https://gerrit.openbmc.org/c/openbmc/dbus-sensors/+/82559Affected platforms: - blyth - blyth2 - bletchley_frontpanel - mudflap - storm_king - storm_king2Change-Id: Iaa5e95ae0758581c015fabe2895f4dd2a34beac7Signed-off-by: Naresh Solanki <naresh.solanki@9elements.com>
configurations: Add IBM's Huygens chassisThis represents the highest level chassis, of which there is one.Signed-off-by: Matt Spinler <spinler@us.ibm.com>Change-Id: I2abfc4732654a6b0592559c56aac
configurations: Add IBM's Huygens chassisThis represents the highest level chassis, of which there is one.Signed-off-by: Matt Spinler <spinler@us.ibm.com>Change-Id: I2abfc4732654a6b0592559c56aacd96f38f4b515
Move the rest of the configsPer the migration we've been doing elsewhere, move the rest of theconfigs into vendor specific folders.Change-Id: Ie688a5c06aa6659f1eea8db99b227dbf3a7c559bSigned-off
Move the rest of the configsPer the migration we've been doing elsewhere, move the rest of theconfigs into vendor specific folders.Change-Id: Ie688a5c06aa6659f1eea8db99b227dbf3a7c559bSigned-off-by: Ed Tanous <etanous@nvidia.com>
configurations/ibm: organize configsOrganizing configs by hardware vendor has some advantages:- quickly find configs for hardware- easily review config changes for hardware you are using via gerr
configurations/ibm: organize configsOrganizing configs by hardware vendor has some advantages:- quickly find configs for hardware- easily review config changes for hardware you are using via gerritpath matches- harder to overlook toplevel files like `VENDORS.md` and `meson.build`- more easily see which config is relevant for some hardwareOrganizing config like this has precedent in linux [1].References:[1] https://github.com/torvalds/linux/tree/b320789d6883cc00ac78ce83bccbfe7ed58afcf0/arch/arm/boot/dtsChange-Id: I8bbca1193a3b4b1b4f1e21b28bdc5a37e63740ffSigned-off-by: Alexander Hansen <alexander.hansen@9elements.com>