On 10/17/2024 12:40 PM, Krzysztof Kozlowski wrote:
On 16/10/2024 16:35, Bjorn Andersson wrote:
@@ -1064,7 +1064,7 @@
};
gpi_dma0: dma-controller@90 {
- #dma-cells = <3>;
+ #dma-cells = <4>;
compati
On 10/17/2024 12:40 PM, Krzysztof Kozlowski wrote:
On 16/10/2024 16:35, Bjorn Andersson wrote:
@@ -1064,7 +1064,7 @@
};
gpi_dma0: dma-controller@90 {
- #dma-cells = <3>;
+ #dma-cells = <4>;
compatibl
On 16/10/2024 16:35, Bjorn Andersson wrote:
>>> @@ -1064,7 +1064,7 @@
>>> };
>>>
>>> gpi_dma0: dma-controller@90 {
>>> - #dma-cells = <3>;
>>> + #dma-cells = <4>;
>>> compatible = "qcom,sc7280-gpi-dma",
>>> "qcom
On Tue, Oct 15, 2024 at 03:33:00PM GMT, Krzysztof Kozlowski wrote:
> On 15/10/2024 14:07, Jyothi Kumar Seerapu wrote:
> > When high performance with multiple i2c messages in a single transfer
> > is required, employ Block Event Interrupt (BEI) to trigger interrupts
> > after specific messages trans
When high performance with multiple i2c messages in a single transfer
is required, employ Block Event Interrupt (BEI) to trigger interrupts
after specific messages transfer and the last message transfer,
thereby reducing interrupts.
For each i2c message transfer, a series of Transfer Request Elemen
On 15/10/2024 14:07, Jyothi Kumar Seerapu wrote:
> When high performance with multiple i2c messages in a single transfer
> is required, employ Block Event Interrupt (BEI) to trigger interrupts
> after specific messages transfer and the last message transfer,
> thereby reducing interrupts.
> For eac