From: Manikanta Mylavarapu <quic_mmanikan@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Kathiravan Thirumoorthy <quic_kathirav@quicinc.com>,
<andersson@kernel.org>, <linus.walleij@linaro.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<konradybcio@kernel.org>, <mturquette@baylibre.com>,
<sboyd@kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Cc: <quic_varada@quicinc.com>, <quic_srichara@quicinc.com>
Subject: Re: [PATCH v3 0/6] Add SPI4 support for IPQ5424
Date: Thu, 2 Jan 2025 11:30:02 +0530 [thread overview]
Message-ID: <dc0b0eef-dcdf-4ed2-a835-d9ca9c5b2c9d@quicinc.com> (raw)
In-Reply-To: <34ab59a1-b735-44d1-918a-1b82954a4423@oss.qualcomm.com>
On 12/30/2024 9:06 PM, Konrad Dybcio wrote:
> On 30.12.2024 4:34 PM, Kathiravan Thirumoorthy wrote:
>>
>>
>> On 12/30/2024 7:28 PM, Konrad Dybcio wrote:
>>> On 30.12.2024 2:54 PM, Konrad Dybcio wrote:
>>>> On 30.12.2024 7:51 AM, Kathiravan Thirumoorthy wrote:
>>>>>
>>>>>
>>>>> On 12/27/2024 12:54 PM, Manikanta Mylavarapu wrote:
>>>>>> Add SPI4 node to the IPQ5424 device tree and update the relevant
>>>>>> bindings, GPIO pin mappings accordingly.
>>>>>>
>>>>>> Changes in V3:
>>>>>> - Rename SPI0 to SPI4 because SPI protocol runs on serial engine 4
>>>>>
>>>>> Do we really need to do this? If so, it will not align with the HW documentation and will lead to the confusion down the line. IMHO, we should stick with the convention followed in the HW documentation.
>>>>
>>>> +1, the clocks are called SPI0/SPI1 internally
>>>
>>> Ok, I looked at a bit more documentation and it looks like
>>> somebody just had fun naming things..
>>>
>>> SPI0 is on SE4 and SPI1 is on something else, with no more
>>> clock provisions for that protocol.. Which is not usually the
>>> case.
>>
>>
>> IPQ5424 has one QUPV3 instance with 6 SEs. SE0-SE4 are Mini core and SE5 is FW core.
>>
>> SE0 and SE1 are for 4-wire UART and 2-wire UART respectively. SE2 and SE3 are for I2C protocol. SE4 is for SPI.
>>
>> Since SE5 is FW based (some RDPs use this SE for I2C). In GCC block, clocks for this instance is named after SPI as SPI1.
>
> Thanks for the explanation.
>
> Manikanta, please refer to this in the commit message as well
>
Thank you, Konrad and Kathiravan, for your valuable insights.
I will incorporate the aforementioned information into the commit message, revert the 'renaming spi0 to spi4',
and include both spi0 and spi1 in the next version.
Thanks & Regards,
Manikanta.
prev parent reply other threads:[~2025-01-02 6:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 7:24 [PATCH v3 0/6] Add SPI4 support for IPQ5424 Manikanta Mylavarapu
2024-12-27 7:24 ` [PATCH v3 1/6] dt-bindings: pinctrl: qcom: rename spi0 pins on IPQ5424 Manikanta Mylavarapu
2024-12-27 7:36 ` Krzysztof Kozlowski
2024-12-27 9:18 ` Manikanta Mylavarapu
2024-12-27 9:30 ` Krzysztof Kozlowski
2024-12-30 7:50 ` Manikanta Mylavarapu
2024-12-30 8:16 ` Krzysztof Kozlowski
2024-12-30 10:47 ` Manikanta Mylavarapu
2024-12-27 7:24 ` [PATCH v3 2/6] dt-bindings: clock: qcom: gcc-ipq5424: add spi4 clocks Manikanta Mylavarapu
2024-12-28 10:09 ` Krzysztof Kozlowski
2024-12-27 7:24 ` [PATCH v3 3/6] pinctrl: qcom: ipq5424: rename spi0 pins Manikanta Mylavarapu
2024-12-27 7:24 ` [PATCH v3 4/6] clk: qcom: ipq5424: rename spi0 clocks Manikanta Mylavarapu
2024-12-28 10:10 ` Krzysztof Kozlowski
2024-12-27 7:24 ` [PATCH v3 5/6] arm64: dts: qcom: ipq5424: add spi4 node Manikanta Mylavarapu
2024-12-27 7:24 ` [PATCH v3 6/6] arm64: dts: qcom: ipq5424: configure spi4 node for rdp466 Manikanta Mylavarapu
2024-12-30 6:51 ` [PATCH v3 0/6] Add SPI4 support for IPQ5424 Kathiravan Thirumoorthy
2024-12-30 13:54 ` Konrad Dybcio
2024-12-30 13:58 ` Konrad Dybcio
2024-12-30 15:34 ` Kathiravan Thirumoorthy
2024-12-30 15:36 ` Konrad Dybcio
2025-01-02 6:00 ` Manikanta Mylavarapu [this message]
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=dc0b0eef-dcdf-4ed2-a835-d9ca9c5b2c9d@quicinc.com \
--to=quic_mmanikan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@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