From: Michal Simek <michal.simek@amd.com>
To: "Patil, Shubham Sanjay" <shubpati@amd.com>,
Rob Herring <robh@kernel.org>
Cc: Shubham Patil <shubhamsanjay.patil@amd.com>,
alexandre.belloni@bootlin.com, Frank.Li@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, git@amd.com
Subject: Re: [PATCH v3 1/3] dt-bindings: i3c: xlnx: Add IBI and hot-join capability properties
Date: Wed, 21 Oct 2026 09:06:50 +0200 [thread overview]
Message-ID: <c1c4d983-795d-4fba-84f5-7bd62246df02@amd.com> (raw)
In-Reply-To: <8547c8c6-502f-4dca-a82f-893a5568f7d6@amd.com>
Hi Rob,
On 10/7/26 08:03, Patil, Shubham Sanjay wrote:
> Hi Rob, Just a reminder !
<snip>
>>>>>> No reason to keep hj because the difference between HJ and IBI is the
>>>>>> address when address arbitration. If hardware support IBI, it should support
>>>>>> HJ. HJ just use special address 0x2.
>>>>>
>>>>> For this IP, they appear to be controlled by different configuration time
>>>>> parameters, so I don't think conflating the two is the right thing to do
>>>>> here:
>>>>> https://docs.amd.com/r/en-US/pg439-axi-i3c/Configuration-Tab
>>>>> Per this doc, and the original commit, hotjoin configuration is not
>>>>> permitted when ibi is not supported but can be enabled and disabled
>>>>> separately when it is.
>>>>
>>>> I am not sure why provide such flexiblity, only difference is that compare
>>>> address 2 or other value.
>>>
>>> It's not unusual for FPGA IPs to provide extreme flexibility so that the
>>> consumption of resources can be kept to a minimum, often to the point of
>>> excessiveness. E.g. for a ethernet MAC IP each individual statistic might
>>> have a configuration option.
>>>
>>>>
>>>> This feature may be quite common for i3c, if other soft IP provider such
>>>> flexiblity, still common property is the better than vendor specific one.
>>>
>>> I'm not at all in favour of speculatively adding properties for
>>> configuration properties of FPGA IPs, particularly given the likelihood
>>> of abuse by others. Without multiple demonstrated users, things shouldn't
>>> be considered for being made common anyway.
>>
>> Rob:
>> What's your opinion? I predict we will met similar problem when
>> I3C become popluar.
>> Do you perfer use vendor property fistly or direct add common
>> property?
>> There will be back compatible problem if change vendor property to
>> common property.
>>
>> Frank
It looks like this thread is stuck and everybody is waiting for your opinion
about it. Can you please take a look when you have time?
Thanks,
Michal
next prev parent reply other threads:[~2026-10-21 7:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 9:42 [PATCH v3 0/3] i3c: master: amd: Add IBI and hot-join support Shubham Patil
2026-09-08 9:42 ` [PATCH v3 1/3] dt-bindings: i3c: xlnx: Add IBI and hot-join capability properties Shubham Patil
2026-09-08 17:54 ` Conor Dooley
2026-09-09 16:21 ` Frank Li
2026-09-10 11:36 ` Conor Dooley
2026-09-10 15:44 ` Frank Li
2026-09-17 11:23 ` Michal Simek
2026-09-22 9:33 ` Conor Dooley
2026-09-22 9:38 ` Conor Dooley
2026-09-22 9:39 ` Conor Dooley
2026-09-22 16:25 ` Frank Li
2026-09-22 17:24 ` Conor Dooley
2026-09-22 18:35 ` Frank Li
2026-09-22 21:29 ` Conor Dooley
2026-09-22 22:21 ` Frank Li
2026-09-23 11:33 ` Patil, Shubham Sanjay
2026-09-23 11:43 ` Conor Dooley
2026-09-23 14:41 ` Frank Li
2026-10-07 6:03 ` Patil, Shubham Sanjay
2026-10-21 7:06 ` Michal Simek [this message]
2026-10-21 15:13 ` Frank Li
2026-10-22 5:12 ` Patil, Shubham Sanjay
2026-09-08 9:42 ` [PATCH v3 2/3] i3c: master: amd: Add support for in-band interrupts Shubham Patil
2026-09-08 10:00 ` sashiko-bot
2026-09-08 9:42 ` [PATCH v3 3/3] i3c: master: amd: Add hot-join support Shubham Patil
2026-09-08 9:55 ` sashiko-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1c4d983-795d-4fba-84f5-7bd62246df02@amd.com \
--to=michal.simek@amd.com \
--cc=Frank.Li@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@amd.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=shubhamsanjay.patil@amd.com \
--cc=shubpati@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox