From: Jeremy Kerr <jk@codeconstruct.com.au>
To: "Aniket ." <aniketmaurya@google.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Joel Stanley <joel@jms.id.au>,
Billy Tsai <billy_tsai@aspeedtech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops
Date: Wed, 26 Jun 2024 17:00:34 +0800 [thread overview]
Message-ID: <d256cd72ef2011c3bfd045b04fb6509d1ac827e9.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAMmmMt25nkZTXXLCVGv1baf3azQR0kwbM8LP4EzCQKOPLUhbVQ@mail.gmail.com>
Hi Aniket,
> > For cases where no other special behaviour is required, we can
> > represent this just as an entry in the OF match table.
>
> Actually I see that IBI support is always present in the HW(DW I3C
> IP). It's just that we have an option in SW to decide whether to
> populate function pointers for IBI or not.
OK, in that case this /definitely/ doesn't belong in the DT then, as
it's purely software configuration.
> So can we remove this selection of ops and always go with ibi ops?
Sounds fine to me, but I don't have direct experience with the non-
ast2600 uses of the dw core.
Cheers,
Jeremy
next prev parent reply other threads:[~2024-06-26 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 5:22 [PATCH 0/2] Select IBI ops for base platform Aniket
2024-06-26 5:22 ` [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops Aniket
2024-06-26 5:31 ` Jeremy Kerr
2024-06-26 8:06 ` Krzysztof Kozlowski
2024-06-26 8:18 ` Jeremy Kerr
2024-06-26 8:52 ` Aniket .
2024-06-26 9:00 ` Jeremy Kerr [this message]
2024-06-26 9:14 ` Aniket .
2024-06-26 10:24 ` Jeremy Kerr
2024-06-27 3:23 ` Aniket .
2024-06-26 5:22 ` [PATCH 2/2] i3c: dw: Select ibi ops for base platform driver Aniket
2024-06-26 8:06 ` Krzysztof Kozlowski
2024-06-27 3:26 ` Aniket .
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=d256cd72ef2011c3bfd045b04fb6509d1ac827e9.camel@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=alexandre.belloni@bootlin.com \
--cc=aniketmaurya@google.com \
--cc=billy_tsai@aspeedtech.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.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).