From: Viken Dadhaniya <quic_vdadhani@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <andi.shyti@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <gregkh@linuxfoundation.org>,
<jirislaby@kernel.org>, <broonie@kernel.or>,
<andersson@kernel.org>, <konradybcio@kernel.org>,
<johan+linaro@kernel.org>, <dianders@chromium.org>,
<agross@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-serial@vger.kernel.org>,
<linux-spi@vger.kernel.org>, <quic_msavaliy@quicinc.com>,
<quic_anupkulk@quicinc.com>
Subject: Re: [PATCH v2 6/8] i2c: qcom-geni: Load i2c qup Firmware from linux side
Date: Mon, 27 Jan 2025 11:10:24 +0530 [thread overview]
Message-ID: <d3447c17-e035-4021-a199-9ff2f4715e1e@quicinc.com> (raw)
In-Reply-To: <CAA8EJprSZx9Bx7EXA_RpwZdhieOLtrTARqXSuo-gO9sVMdK5Qg@mail.gmail.com>
On 1/24/2025 9:25 PM, Dmitry Baryshkov wrote:
> On Fri, 24 Jan 2025 at 17:24, Viken Dadhaniya <quic_vdadhani@quicinc.com> wrote:
>>
>>
>>
>> On 1/24/2025 8:34 PM, Dmitry Baryshkov wrote:
>>> On Fri, Jan 24, 2025 at 04:23:07PM +0530, Viken Dadhaniya wrote:
>>>> Add provision to load firmware of Serial engine for I2C protocol from
>>>> Linux Execution Environment on running on APPS processor.
>>>>
>>>> Co-developed-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
>>>> Signed-off-by: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>
>>>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>>>> ---
>>>> drivers/i2c/busses/i2c-qcom-geni.c | 7 +++++--
>>>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/i2c/busses/i2c-qcom-geni.c b/drivers/i2c/busses/i2c-qcom-geni.c
>>>> index 7bbd478171e0..9ad3b8c9a224 100644
>>>> --- a/drivers/i2c/busses/i2c-qcom-geni.c
>>>> +++ b/drivers/i2c/busses/i2c-qcom-geni.c
>>>> @@ -872,8 +872,11 @@ static int geni_i2c_probe(struct platform_device *pdev)
>>>> }
>>>> proto = geni_se_read_proto(&gi2c->se);
>>>> if (proto != GENI_SE_I2C) {
>>>> - ret = dev_err_probe(dev, -ENXIO, "Invalid proto %d\n", proto);
>>>> - goto err_resources;
>>>> + ret = geni_load_se_firmware(&gi2c->se, GENI_SE_I2C);
>>>
>>> Hmm, so if the SE has been configured to e.g. SPI by the TZ, can we
>>> switch it to the I2C?
>>
>> No, in the current design, TZ will not load the SE firmware.
>
> But that's what your patch is doing: if the protocol is not I2C, try
> switching to I2C.
>
> Instead it should be 'if unconfigured, try loading I2C'.
Sure, I will update it in the next patch.
>
>>
>>>
>>>> + if (ret) {
>>>> + dev_err(gi2c->se.dev, "i2c firmware load failed ret: %d\n", ret);
>>>> + goto err_resources;
>>>> + }
>>>> }
>>>>
>>>> if (desc && desc->no_dma_support)
>>>> --
>>>> 2.34.1
>>>>
>>>
>
>
>
next prev parent reply other threads:[~2025-01-27 5:40 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 10:53 [PATCH v2 0/8] Add support to load QUP SE firmware from Viken Dadhaniya
2025-01-24 10:53 ` [PATCH v2 1/8] dt-bindings: qcom: geni-se: Add 'firmware-name' property for firmware loading Viken Dadhaniya
2025-01-24 11:00 ` Krzysztof Kozlowski
2025-01-24 11:33 ` Viken Dadhaniya
2025-01-24 10:53 ` [PATCH v2 2/8] dt-bindings: i2c: qcom,i2c-geni: Add support for selecting data transfer mode Viken Dadhaniya
2025-01-24 11:18 ` Dmitry Baryshkov
2025-01-24 12:22 ` Viken Dadhaniya
2025-01-24 15:03 ` Dmitry Baryshkov
2025-01-24 15:16 ` Viken Dadhaniya
2025-01-27 6:58 ` Krzysztof Kozlowski
2025-01-24 10:53 ` [PATCH v2 3/8] spi: dt-bindings: " Viken Dadhaniya
2025-01-27 6:59 ` Krzysztof Kozlowski
2025-01-24 10:53 ` [PATCH v2 4/8] dt-bindings: serial: " Viken Dadhaniya
2025-01-27 7:02 ` Krzysztof Kozlowski
2025-01-27 14:27 ` Dmitry Baryshkov
2025-01-27 16:24 ` Krzysztof Kozlowski
2025-01-27 17:50 ` Konrad Dybcio
2025-01-28 11:40 ` Konrad Dybcio
2025-01-29 2:21 ` Dmitry Baryshkov
2025-01-29 7:23 ` Krzysztof Kozlowski
2025-01-29 8:18 ` neil.armstrong
2025-02-09 10:11 ` Viken Dadhaniya
2025-02-09 10:19 ` Krzysztof Kozlowski
2025-02-10 7:01 ` Viken Dadhaniya
2025-02-09 10:27 ` Viken Dadhaniya
2025-01-24 10:53 ` [PATCH v2 5/8] soc: qcom: geni-se: Add support to load QUP SE Firmware via Linux subsystem Viken Dadhaniya
2025-01-27 7:06 ` Krzysztof Kozlowski
2025-03-03 12:47 ` Viken Dadhaniya
2025-01-27 12:07 ` Mukesh Kumar Savaliya
2025-01-24 10:53 ` [PATCH v2 6/8] i2c: qcom-geni: Load i2c qup Firmware from linux side Viken Dadhaniya
2025-01-24 15:04 ` Dmitry Baryshkov
2025-01-24 15:24 ` Viken Dadhaniya
2025-01-24 15:55 ` Dmitry Baryshkov
2025-01-27 5:40 ` Viken Dadhaniya [this message]
2025-01-24 10:53 ` [PATCH v2 7/8] spi: geni-qcom: Load spi " Viken Dadhaniya
2025-01-24 10:53 ` [PATCH v2 8/8] serial: qcom-geni: Load UART " Viken Dadhaniya
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=d3447c17-e035-4021-a199-9ff2f4715e1e@quicinc.com \
--to=quic_vdadhani@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=broonie@kernel.or \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=quic_anupkulk@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--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