org.infradead.lists.linux-i3c archive
575 archived articles, newest first (page 6 of 6). Latest articles →
[PATCH v10 1/2] dt-bindings: i3c: Add AMD I3C master controller support
Thu, 9 Jul 2026 12:12:32 +0530[PATCH v10 0/2] Add AMD I3C master controller driver and bindings
Thu, 9 Jul 2026 12:12:31 +0530Re: RE: RE: [PATCH] i3c: master: dw-i3c-master: fix OD timing for first broadcast
Thu, 9 Jul 2026 06:42:24 +0000RE: [EXT] Re: [PATCH v13 3/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator
Thu, 9 Jul 2026 04:49:26 +0000Re: [PATCH v6 5/5] i3c: master: Add optional_bytes for variable-length GET CCC validation
Wed, 8 Jul 2026 22:37:16 -0500Re: [PATCH v6 5/5] i3c: master: Add optional_bytes for variable-length GET CCC validation
Thu, 9 Jul 2026 02:56:37 +0000Re: [PATCH v13 3/7] mfd: p3h2x4x: Add driver for NXP P3H2x4x i3c hub and on-die regulator
Wed, 8 Jul 2026 20:20:34 +0100Re: [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB
Wed, 8 Jul 2026 11:45:51 -0400Re: [PATCH v6 4/5] i3c: master: Validate GET CCC payload length and retry Direct GET once
Wed, 08 Jul 2026 17:19:44 +0200Re: [PATCH v6 5/5] i3c: master: Add optional_bytes for variable-length GET CCC validation
Wed, 8 Jul 2026 10:01:05 -0500Re: [PATCH v6 4/5] i3c: master: Validate GET CCC payload length and retry Direct GET once
Wed, 8 Jul 2026 09:53:46 -0500Re: [PATCH v6 2/5] i3c: master: Report actual GET CCC payload length on success
Wed, 08 Jul 2026 16:52:26 +0200Re: [PATCH v6 1/5] i3c: ccc: Add actual_len to struct i3c_ccc_cmd_payload
Wed, 08 Jul 2026 16:52:26 +0200Re: [PATCH v6 3/5] i3c: master: dw: Map CCC hardware errors to I3C M0/M2
Wed, 8 Jul 2026 08:20:34 -0500Re: [PATCH v6 2/5] i3c: master: Report actual GET CCC payload length on success
Wed, 8 Jul 2026 08:16:56 -0500Re: [PATCH v6 1/5] i3c: ccc: Add actual_len to struct i3c_ccc_cmd_payload
Wed, 8 Jul 2026 08:11:56 -0500Re: [PATCH v6 4/5] i3c: master: Validate GET CCC payload length and retry Direct GET once
Wed, 08 Jul 2026 10:01:41 +0000Re: [PATCH v6 2/5] i3c: master: Report actual GET CCC payload length on success
Wed, 08 Jul 2026 09:44:28 +0000[PATCH v6 4/5] i3c: master: Validate GET CCC payload length and retry Direct GET once
Wed, 8 Jul 2026 00:17:40 -0700[PATCH v6 5/5] i3c: master: Add optional_bytes for variable-length GET CCC validation
Wed, 8 Jul 2026 00:17:41 -0700[PATCH v6 3/5] i3c: master: dw: Map CCC hardware errors to I3C M0/M2
Wed, 8 Jul 2026 00:17:39 -0700[PATCH v6 2/5] i3c: master: Report actual GET CCC payload length on success
Wed, 8 Jul 2026 00:17:38 -0700[PATCH v6 0/5] i3c: Improve CCC reliability with actual_len, validation, and Direct GET retry
Wed, 8 Jul 2026 00:17:36 -0700[PATCH v6 1/5] i3c: ccc: Add actual_len to struct i3c_ccc_cmd_payload
Wed, 8 Jul 2026 00:17:37 -0700Re: [PATCH 1/2] dt-bindings: i3c: add binding for Realtek RTS490x I3C HUB
Tue, 7 Jul 2026 07:28:28 +0000Re: [PATCH v13 5/7] i3c: hub: Add support for the I3C interface in the I3C hub
Mon, 6 Jul 2026 12:55:54 -0400Re: [PATCH v5 3/5] i3c: master: dw: Map CCC hardware errors to I3C M0/M2
Mon, 6 Jul 2026 05:56:37 +0000Re: [PATCH v5 2/5] i3c: master: Report actual GET CCC payload length on success
Mon, 6 Jul 2026 05:28:35 +0000Re: [PATCH v2] i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices
Sun, 5 Jul 2026 23:34:47 +0200Re: [PATCH] i3c: master: adi: initialize the lock before enabling interrupts
Sun, 5 Jul 2026 23:29:24 +0200Re: [PATCH] i3c: master: svc: report timeout waiting for STOP idle
Sun, 5 Jul 2026 23:29:15 +0200Re: [PATCH v2] i3c: master: svc: bound IBI payload to the requested max_payload_len
Sun, 5 Jul 2026 23:29:07 +0200Re: [PATCH v5 2/5] i3c: master: Report actual GET CCC payload length on success
Fri, 03 Jul 2026 11:06:38 +0000Re: [PATCH v5 3/5] i3c: master: dw: Map CCC hardware errors to I3C M0/M2
Fri, 03 Jul 2026 10:59:30 +0000[PATCH v5 5/5] i3c: master: Add optional_bytes for variable-length GET CCC validation
Fri, 3 Jul 2026 03:51:17 -0700[PATCH v5 4/5] i3c: master: Validate GET CCC payload length and retry Direct GET once
Fri, 3 Jul 2026 03:51:16 -0700[PATCH v5 3/5] i3c: master: dw: Map CCC hardware errors to I3C M0/M2
Fri, 3 Jul 2026 03:51:15 -0700[PATCH v5 2/5] i3c: master: Report actual GET CCC payload length on success
Fri, 3 Jul 2026 03:51:14 -0700[PATCH v5 1/5] i3c: ccc: Add actual_len to struct i3c_ccc_cmd_payload
Fri, 3 Jul 2026 03:51:13 -0700[PATCH v5 0/5] i3c: Improve CCC reliability with actual_len, validation, and Direct GET retry
Fri, 3 Jul 2026 03:51:12 -0700RE: [PATCH v13 5/7] i3c: hub: Add support for the I3C interface in the I3C hub
Fri, 3 Jul 2026 10:50:30 +0000Re: [PATCH v4 3/3] i3c: master: Validate GET CCC payload length and retry Direct GET once
Fri, 3 Jul 2026 09:16:23 +0000Re: [PATCH v4 1/3] i3c: master: dw: Report actual GET CCC payload length on success
Fri, 3 Jul 2026 09:09:24 +0000Re: [PATCH v5 04/12] i3c: master: Add support for devices using SETAASA
Fri, 3 Jul 2026 09:08:55 +0000Re: [PATCH v4 3/3] i3c: master: Validate GET CCC payload length and retry Direct GET once
Fri, 3 Jul 2026 08:58:21 +0000Re: [PATCH] i3c: master: Fix device_register() error path
Thu, 2 Jul 2026 15:16:56 -0400Re: [PATCH] i3c: master: Fix device_register() error path
Thu, 02 Jul 2026 19:00:02 +0000[PATCH] i3c: master: Fix device_register() error path
Thu, 2 Jul 2026 21:36:44 +0300Re: [PATCH RFC RESEND 1/7] i3c: master: Support IBI-based wakeup capability
Thu, 2 Jul 2026 10:10:52 -0400Re: [PATCH RFC RESEND 2/7] i3c: master: Report wakeup events for IBIs
Thu, 2 Jul 2026 13:38:44 +0300Re: [PATCH] i3c: master: renesas: reset xfer status before each wait
Thu, 2 Jul 2026 12:06:42 +0300Re: [PATCH RFC RESEND 2/7] i3c: master: Report wakeup events for IBIs
Wed, 01 Jul 2026 20:33:36 +0000Re: [PATCH RFC RESEND 3/7] i3c: master: Add helper to query bus wakeup requirements
Wed, 01 Jul 2026 20:33:14 +0000Re: [PATCH RFC RESEND 5/7] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
Wed, 01 Jul 2026 20:33:08 +0000Re: [PATCH RFC RESEND 1/7] i3c: master: Support IBI-based wakeup capability
Wed, 01 Jul 2026 20:30:53 +0000Re: [PATCH RFC RESEND 4/7] i3c: master: Reject IBI requests from non-IBI-capable devices
Wed, 01 Jul 2026 20:29:04 +0000Re: [PATCH RFC 2/7] i3c: master: Report wakeup events for IBIs
Wed, 01 Jul 2026 20:27:22 +0000Re: [PATCH RFC 5/7] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
Wed, 01 Jul 2026 20:26:40 +0000Re: [PATCH RFC 1/7] i3c: master: Support IBI-based wakeup capability
Wed, 01 Jul 2026 20:26:23 +0000Re: [PATCH RFC RESEND 6/7] i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev()
Wed, 01 Jul 2026 20:23:09 +0000Re: [PATCH RFC 3/7] i3c: master: Add helper to query bus wakeup requirements
Wed, 01 Jul 2026 20:23:01 +0000Re: [PATCH RFC RESEND 7/7] i3c: mipi-i3c-hci: Advertise IBI wakeup capability
Wed, 01 Jul 2026 20:22:33 +0000[PATCH RFC RESEND 7/7] i3c: mipi-i3c-hci: Advertise IBI wakeup capability
Wed, 1 Jul 2026 23:15:33 +0300[PATCH RFC RESEND 6/7] i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev()
Wed, 1 Jul 2026 23:15:32 +0300[PATCH RFC RESEND 5/7] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
Wed, 1 Jul 2026 23:15:31 +0300[PATCH RFC RESEND 4/7] i3c: master: Reject IBI requests from non-IBI-capable devices
Wed, 1 Jul 2026 23:15:30 +0300[PATCH RFC RESEND 3/7] i3c: master: Add helper to query bus wakeup requirements
Wed, 1 Jul 2026 23:15:29 +0300[PATCH RFC RESEND 2/7] i3c: master: Report wakeup events for IBIs
Wed, 1 Jul 2026 23:15:28 +0300[PATCH RFC RESEND 1/7] i3c: master: Support IBI-based wakeup capability
Wed, 1 Jul 2026 23:15:27 +0300[PATCH RFC RESEND 0/7] i3c: Support IBI-based system wakeup
Wed, 1 Jul 2026 23:15:26 +0300Re: [PATCH RFC 0/7] i3c: Support IBI-based system wakeup
Wed, 1 Jul 2026 23:15:16 +0300[PATCH RFC 7/7] i3c: mipi-i3c-hci: Advertise IBI wakeup capability
Wed, 1 Jul 2026 23:05:52 +0300[PATCH RFC 6/7] i3c: mipi-i3c-hci: Factor out i3c_hci_sysdev()
Wed, 1 Jul 2026 23:05:51 +0300[PATCH RFC 5/7] i3c: mipi-i3c-hci-pci: Propagate I3C wakeup requirements to PCI
Wed, 1 Jul 2026 23:05:50 +0300[PATCH RFC 4/7] i3c: master: Reject IBI requests from non-IBI-capable devices
Wed, 1 Jul 2026 23:05:49 +0300
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.