[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a85859a-9487-48fd-b1cb-a4a4195a8e63@linaro.org>
Date: Wed, 4 Dec 2024 16:25:23 +0100
From: neil.armstrong@...aro.org
To: Viken Dadhaniya <quic_vdadhani@...cinc.com>, andi.shyti@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
gregkh@...uxfoundation.org, jirislaby@...nel.org, broonie@...nel.or,
andersson@...nel.org, konradybcio@...nel.org, johan+linaro@...nel.org,
dianders@...omium.org, agross@...nel.org, linux-arm-msm@...r.kernel.org,
linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
linux-spi@...r.kernel.org
Cc: =quic_msavaliy@...cinc.com, quic_anupkulk@...cinc.com,
Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Subject: Re: [PATCH v1 1/7] dt-bindings: i2c: qcom,i2c-geni: Document DT
properties for QUP firmware loading
On 04/12/2024 16:03, Viken Dadhaniya wrote:
> Document the 'qcom,load-firmware' and 'qcom,xfer-mode' properties to
> support SE(Serial Engine) firmware loading from the protocol driver and to
> select the data transfer mode, either GPI DMA (Generic Packet Interface)
> or non-GPI mode (PIO/CPU DMA).
>
> I2C controller can operate in one of two modes based on the
> 'qcom,xfer-mode' property, and the firmware is loaded accordingly.
>
> Co-developed-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
> Signed-off-by: Viken Dadhaniya <quic_vdadhani@...cinc.com>
> ---
> .../devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> index 9f66a3bb1f80..a26f34fce1bb 100644
> --- a/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> +++ b/Documentation/devicetree/bindings/i2c/qcom,i2c-geni-qcom.yaml
> @@ -66,6 +66,15 @@ properties:
> required-opps:
> maxItems: 1
>
> + qcom,load-firmware:
> + type: boolean
> + description: Optional property to load SE (serial engine) Firmware from protocol driver.
> +
> + qcom,xfer-mode:
> + description: Value 1,2 and 3 represents FIFO, CPU DMA and GSI DMA mode respectively.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [1, 2, 3]
In the code, FIFO mode is default if not specified, please precise it in the
bindings aswell.
Thanks,
Neil
> +
> required:
> - compatible
> - interrupts
> @@ -142,5 +151,7 @@ examples:
> interconnect-names = "qup-core", "qup-config", "qup-memory";
> power-domains = <&rpmhpd SC7180_CX>;
> required-opps = <&rpmhpd_opp_low_svs>;
> + qcom,load-firmware;
> + qcom,xfer-mode = <1>;
> };
> ...
Powered by blists - more mailing lists