[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241001-i3c_dts_assign-v1-0-6ba83dc15eb8@nxp.com>
Date: Tue, 01 Oct 2024 13:08:19 -0400
From: Frank Li <Frank.Li@....com>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: linux-i3c@...ts.infradead.org, linux-kernel@...r.kernel.org,
arnd@...db.de, bbrezillon@...nel.org, boris.brezillon@...labora.com,
conor.culhane@...vaco.com, gregkh@...uxfoundation.org, imx@...ts.linux.dev,
miquel.raynal@...tlin.com, pthombar@...ence.com,
ravindra.yashvant.shinde@....com, Frank Li <Frank.Li@....com>,
stable@...nel.org
Subject: [PATCH 0/3] I3C: master: fix the address assign issue if
assign-address is exist in dts
These patches are split from
https://lore.kernel.org/linux-i3c/ZvrAuOBLgi+HtrPD@lizhi-Precision-Tower-5810/#R
There are discussion on
https://lore.kernel.org/linux-i3c/20240819-i3c_fix-v3-0-7d69f7b0a05e@nxp.com/T/#m16fa9bb875b0ae9d37c5f6e91f90e375551c6366
Basic back ground is
The current framework is
1. get free i3c dynamic address
2. if found dt have assign-address for such device (identify by PID),
change to such address.
There are problem in current implement.
If device A have assign-address 0xa, device B have assign-address 0xB,
which described at dts file.
If device A is not ready during i3c probe, and device B hotjoin happen,
0xA will assign to device B, so if device A hotjoin later, address 0xA
Can't assign to A because B already use it.
Mirquel's opinion is return address B when B hotjoin by scan dts by PID.
The issue is the controller HCI (i3C standard),
I3C HCI Spec 1.2, sec 6.4.1, when do DAA, "DAA CMD and dynmatic address"
queue to cmd together. We don't know PID before DAA CMD. So dynamic
address can NOT get based on PID.
When do DAA in HCI, it needs a dynamtic address firstly before get PID
information.
Consider this need more time to discuss, so split from previous big serial
to avoid prevent other fix patches can't be merged into i3c tree.
This patches's overall design:
1. keep current frame's work flow
2. reserver all address, which assigned in dts.
3. the device with assigned address have high priorioty to get such
address.
4. if all address without assigned by dt are used, use offline devices's
assigned address.
To: Alexandre Belloni <alexandre.belloni@...tlin.com>
Cc: linux-i3c@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org
Cc: arnd@...db.de
Cc: bbrezillon@...nel.org
Cc: boris.brezillon@...labora.com
Cc: conor.culhane@...vaco.com
Cc: gregkh@...uxfoundation.org
Cc: imx@...ts.linux.dev
Cc: linux-i3c@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org
Cc: miquel.raynal@...tlin.com
Cc: pthombar@...ence.com
Cc: ravindra.yashvant.shinde@....com
Signed-off-by: Frank Li <Frank.Li@....com>
---
Frank Li (3):
i3c: master: Replace hard code 2 with macro I3C_ADDR_SLOT_STATUS_BITS
i3c: master: Extend address status bit to 4 and add I3C_ADDR_SLOT_EXT_INIT
i3c: master: Fix dynamic address leak when 'assigned-address' is present
drivers/i3c/master.c | 85 +++++++++++++++++++++++++++++++++++-----------
include/linux/i3c/master.h | 9 +++--
2 files changed, 72 insertions(+), 22 deletions(-)
---
base-commit: 77df9e4bb2224d8ffbddec04c333a9d7965dad6c
change-id: 20241001-i3c_dts_assign-d615fc33cc1d
Best regards,
---
Frank Li <Frank.Li@....com>
Powered by blists - more mailing lists