[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMmmMt3DZWA734iFGLxz7cj+hYiWgq5MDOrc_UJpYeaij+yywg@mail.gmail.com>
Date: Wed, 26 Jun 2024 14:44:32 +0530
From: "Aniket ." <aniketmaurya@...gle.com>
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Alexandre Belloni <alexandre.belloni@...tlin.com>, Joel Stanley <joel@....id.au>,
Billy Tsai <billy_tsai@...eedtech.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, linux-i3c@...ts.infradead.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops
> > 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.
I am using dw core directly through Synopsys virtualizer development
kit(VDK) setup.
I think it should be fine to always have the all ops supported in the
SW as they are in HW.
Shall I remove the ibi_capable property from the dw_i3c_master struct?
Thanks,
Aniket.
Powered by blists - more mailing lists