Jarkko Nikula 9e0e9e85e7 i3c: mipi-i3c-hci: Report NACK response from CCC command to core ... Currently probe of mipi-i3c-hci will fail if bus doesn't have any I3C devices connected. This happens when CCC commands that are sent during i3c_master_bus_init() are not ACKed by any device and controller responds with an error status set. The controller can detect NACK both during I3C address header transmission (broadcast address 0x7e is not ACKed) and when target device address or dynamic address assignment is NACKed. Former as error status 0x4: Address Header Error and latter as 0x5: NACK. Difference between those two NACK statuses were not described explicitly until MIPI I3C HCI Specification v1.1. Earlier versions share the same error status code though. Report both of those as I3C_ERROR_M2 to I3C core code. Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com> Link: https://lore.kernel.org/r/20231109133708.653950-2-jarkko.nikula@linux.intel.com Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>		2023-11-16 23:36:44 +01:00
..
master	i3c: mipi-i3c-hci: Report NACK response from CCC command to core	2023-11-16 23:36:44 +01:00
device.c	driver core: make struct device_type.uevent() take a const *	2023-01-27 13:45:36 +01:00
internals.h	i3c: export SETDASA method	2022-12-11 21:25:58 +01:00
Kconfig	i3c: Add core I3C infrastructure	2018-11-12 10:33:49 +01:00
Makefile	i3c: Add core I3C infrastructure	2018-11-12 10:33:49 +01:00
master.c	I3C for 6.7	2023-11-04 16:25:36 -10:00