From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jorge Marques <gastmaier@gmail.com>
Cc: Jorge Marques <jorge.marques@analog.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Frank Li <Frank.Li@nxp.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-i3c@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: i3c: Add adi-i3c-master
Date: Fri, 27 Jun 2025 16:49:19 +0200 [thread overview]
Message-ID: <41782ded-908b-46ef-8f75-4d2565476b7c@kernel.org> (raw)
In-Reply-To: <tl5fckhrivaqfyzwyb2o2a7gykpigwend7z2nduqgbbej3hqbs@vxxtsadhtdmt>
On 27/06/2025 16:38, Jorge Marques wrote:
> On Fri, Jun 27, 2025 at 08:56:55AM +0200, Krzysztof Kozlowski wrote:
>> On Thu, Jun 26, 2025 at 12:07:36PM +0200, Jorge Marques wrote:
>>> Add bindings doc for ADI I3C Controller IP core, a FPGA synthesizable IP
>>> core that implements the MIPI I3C Basic controller specification.
>>
>> How did you resolve my last comment? I don't see any explanation -
>> neither here nor in the binding description. Binding description is
>> actually better place, I think now.
>>
>> Best regards,
>> Krzysztof
>>
>
> Hi Krzysztof,
>
> I forgot to condense out discussion on v4.
> What about this binding description:
>
> description: |
> FPGA-based I3C controller designed to interface with I3C and I2C
> peripherals, implementing a subset of the I3C-basic specification.
> The IP core is tested on arm, microblaze, and arm64 architectures.
> It takes one or two clocks, axi and i3c. If only axi is provided,
> then there is no clock signal to the i3c input clock pin and axi
This is obvious from the schema, drop.
> clock drives the whole IP. The compatible is suffixed by 1.00.a
> foreseeing future controllers by Analog Devices Inc. and breaking
> changes.
I don't understand that. How are you breaking any changes? And how
1.00.a predicts future? I don't think this reflects previous discussion.
Why you were asked to go with v1.00.a?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-27 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 10:07 [PATCH v4 0/2] Add ADI I3C Controller Jorge Marques
2025-06-26 10:07 ` [PATCH v4 1/2] dt-bindings: i3c: Add adi-i3c-master Jorge Marques
2025-06-26 16:13 ` Frank Li
2025-06-27 6:56 ` Krzysztof Kozlowski
2025-06-27 14:38 ` Jorge Marques
2025-06-27 14:49 ` Krzysztof Kozlowski [this message]
2025-06-27 16:02 ` Jorge Marques
2025-07-02 10:58 ` Jorge Marques
2025-07-02 11:38 ` Conor Dooley
2025-07-11 8:14 ` Jorge Marques
2025-07-11 16:28 ` Conor Dooley
2025-07-14 9:53 ` Jorge Marques
2025-07-02 14:23 ` Marcelo Schmitt
2025-07-02 15:04 ` Conor Dooley
2025-06-26 10:07 ` [PATCH v4 2/2] i3c: master: Add driver for Analog Devices I3C Controller IP Jorge Marques
2025-06-26 16:51 ` Frank Li
2025-06-27 14:10 ` Jorge Marques
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=41782ded-908b-46ef-8f75-4d2565476b7c@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gastmaier@gmail.com \
--cc=jorge.marques@analog.com \
--cc=krzk+dt@kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).