Milton D. Miller II

My understanding of w1 (which is from ancient memory seeing technology demos, white papers, etc, and reading Linux kernel driver code) is that the id address, `00.400000000000.46`, is supposed to...

Considering that https://github.com/openbmc/linux/commit/b87cf9118e03d8a83039c88fa348165148f5d487 is a kconfig change that implies CONFIG_SMP was already broken do you plan to bisect that config (I'd expect on UP qemu to be a sufficient test)?

Actually, taking a look, this occurs when`CONFIG_JFFS2_FS_WRITEBUFFER` is enabled but the flash does not require a write buffer (because its not UBI, NAND, or DATAFLASH, and the NOR was flagged...

The issue appears when the write buffer is configured but not required. I don't remember if its only a lockdep issue or only an issue when lockdep is enabled. If...

This is dev_set_name. Was there a trigger? Is the driver trying to set the name after the device was added?

No device driver found the desired hardware. Look at the kernel log for error message. Look under `/sys/bus/` by connection type if your device is not present. Check the device...

Do you have `CONIFG_SENSORS_W83795=y` in your kernel config? Yocto uses small cfg snippets to enable drivers that exist on your hardware.

All I can say is look at sysfs and dmesg again. You found the device; if the driver is bound you should find a `driver` symlink. If not look for...

https://github.com/openbmc/docs/blob/master/development/add-new-system.md#hwmon-sensors

I seem to remember some deferral infrastructure, probably for scsi or usb, but will search later.