Simone
694ed6a712
Call i2c_register_spd() per adapter, like i801 and piix4, instead of
telling the user to echo into new_device. The helper counts populated
slots from DMI and probes upwards from 0x50 via i2c_new_scanned_device(),
so it claims no address that does not answer; each channel carries half
the DIMMs and the scan is per adapter, so each finds its own. Verified:
four clients on load, two per channel, none on the empty slots, and
decode-dimms works with no manual step.
This needed Receive Byte to be worth doing — without I2C_FUNC_SMBUS_BYTE
ee1004 would not have bound to what was instantiated.
The write_disable variant is deliberate. This part is DDR4 only, where
the two are equivalent (the split gates spd5118 on DDR5), and of two
equivalent calls the one that does not read as "this driver enables SPD
writes" is the better name to leave in a driver whose bus is the memory
bus. In-tree convention is write_enable; the cover letter offers to
switch.
Kconfig gains select I2C_SMBUS.
Out-of-tree, compat.h maps the call onto the older unsplit
i2c_register_spd() where that is what the target kernel has. It is force
included from the Makefile so i2c-imc-skylake.c stays byte-identical to
the submitted file, and the Makefile detects the API by grepping the
target kernel's header rather than testing a version number, which keeps
it correct on backported trees. Builds clean against both 6.8 and 7.0
headers; DKMS 1.0.2 installs on all four kernels here.
test-smoke.sh needed two fixes to keep testing what it claims:
- A bound driver owns its address, so the raw transaction checks lost
the SPDs the moment the driver started instantiating them. The script
now unbinds ee1004 for the duration rather than deleting the clients:
sysfs delete_device only removes clients that new_device created,
and unbinding is sufficient because i2c-dev refuses an address only
while a driver is bound (i2cdev_check: `return dev->driver ? -EBUSY
: 0`). Rebound from an EXIT trap.
- Those checks were guarded on an SPD address having been found, and
when the lookup failed they vanished from the run silently: the suite
reported "12 passed, 0 failed" while seven checks had not executed.
Skipped checks are now counted and printed, which is how the above
was noticed at all.
Smoke suite: 20 passed, 0 failed, 0 skipped. checkpatch --strict 0/0/0,
in-tree W=1 and Sparse clean.
27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
config I2C_IMC_SKYLAKE
|
|
tristate "Intel Skylake-X iMC SMBus adapter"
|
|
depends on PCI && (X86_64 || COMPILE_TEST)
|
|
select I2C_SMBUS
|
|
help
|
|
Say Y here if you want kernel support for the integrated memory
|
|
controller (iMC) SMBus engine found in Intel Skylake-X / Cascade
|
|
Lake-X processors (socket LGA 2066, platform X299, PCU function
|
|
8086:2085).
|
|
|
|
Two I2C adapters are registered, one per hardware SMBus channel,
|
|
allowing access to DDR4 DIMM SPD EEPROMs (0x50-0x57) and thermal
|
|
sensors from userspace via standard i2c-tools and lm-sensors.
|
|
SPD EEPROMs are instantiated automatically from DMI, so decode-dimms
|
|
works without any manual step.
|
|
|
|
Firmware, SMM, a BMC or CLTT may drive the same engine and no
|
|
generic arbitration mechanism is known. The driver therefore
|
|
refuses to bind unless the allow_unsafe_access module parameter
|
|
is enabled. See Documentation/i2c/busses/i2c-imc-skylake.rst.
|
|
|
|
If unsure, say N. This driver is only useful on Intel X299 desktop
|
|
/ HEDT systems with the Skylake-X or Cascade Lake-X CPU.
|
|
|
|
This driver can also be built as a module. If so, the module
|
|
will be called i2c-imc-skylake.
|