From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Komal Bajaj <quic_kbajaj@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Abel Vesa <abel.vesa@linaro.org>,
Rishabh Bhatnagar <rishabhb@codeaurora.org>,
Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v2 2/5] dt-bindings: arm: msm: Add bindings for multi channel DDR in LLCC
Date: Thu, 6 Apr 2023 15:22:39 +0530 [thread overview]
Message-ID: <d7d03e81-03d6-b643-a2e6-0867bab7e0ef@quicinc.com> (raw)
In-Reply-To: <c8f3499f-d927-6657-c7c6-732ed2222525@quicinc.com>
On 4/6/2023 2:49 PM, Komal Bajaj wrote:
> Didn't see my reply on the list, so sending it again.
> And also I see that the dt patch is already applied.
The reason why you are not seeing your replies at
https://lore.kernel.org/lkml/20230313124040.9463-1-quic_kbajaj@quicinc.com/
is because your reply cc-list contain some invalid domain
(codeaurora.org) email id's and any list/email mentioned
after that would not be getting your emails.
-- Mukesh
>
> Thanks Krzysztof and Manivannan for reviewing the patch.
>
>
> On 3/15/2023 7:18 PM, Manivannan Sadhasivam wrote:
>> On Wed, Mar 15, 2023 at 08:41:21AM +0100, Krzysztof Kozlowski wrote:
>>> On 13/03/2023 13:40, Komal Bajaj wrote:
>>>> Add description for additional nodes needed to support
>>>> mulitple channel DDR configurations in LLCC.
>>>>
>>>> Signed-off-by: Komal Bajaj<quic_kbajaj@quicinc.com>
>>> +Cc Mani,
>>>
>> Thanks, Krzysztof!
>>
>>> This will conflict with:
>>> https://lore.kernel.org/all/20230314080443.64635-3-manivannan.sadhasivam@linaro.org/
>>>
>>> Please rebase on top of Mani's patches (assuming they are not
>>> conflicting in principle)
>>>
>>>> ---
>>>> Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml | 9 +++++++++
>>>> 1 file changed, 9 insertions(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml
>>>> index 38efcad56dbd..9a4a76caf490 100644
>>>> --- a/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml
>>>> +++ b/Documentation/devicetree/bindings/arm/msm/qcom,llcc.yaml
>>>> @@ -37,15 +37,24 @@ properties:
>>>> items:
>>> minItems: 2
>>>
>>>> - description: LLCC base register region
>>>> - description: LLCC broadcast base register region
>>>> + - description: Feature register to decide which LLCC configuration
>>>> + to use, this is optional
>>>>
>>>> reg-names:
>>> minItems: 2
>>>
>>>> items:
>>>> - const: llcc_base
>>>> - const: llcc_broadcast_base
>>>> + - const: multi_channel_register
>> Is this the actual register region or a specific register offset? We generally
>> try to pass the base address of the region along with the size and use the
>> offset inside the driver to access any specific registers.
>>
>> Thanks,
>> Mani
>
> This is a specific register offset outside the LLCC register region which has the
> information of number of DDR channel.
>
>>>>
>>>> interrupts:
>>>> maxItems: 1
>>>>
>>>> + multi-ch-bit-off:
>>>> + items:
>>>> + - description: Specifies the offset in bits into the multi_channel_register
>>>> + and the number of bits used to decide which LLCC configuration
>>>> + to use
>>> There are here few issues.
>>> First, I don't fully understand the property. What is an LLCC
>>> configuration? Like some fused values?
>
> There are different configuration for LLCC based on the number of
> DDR channel it uses. Here, we are basically trying to get information
> about the same.
>
>>> Second, don't make it a register specific, it will not scale easily to
>>> any new version of this interface. Although how this should look like
>>> depends on what is it.
>
> LLCC driver can only get DDR channel information from the register.
>
>>> Third, you need vendor prefix and type (unless this is a generic
>>> property, but does not look like). Then "items" is probably wrong. Line
>>> break after "description: "
>
> Noted, will take care of this in the next patchset.
>
> Thanks
> Komal
>
>>> Best regards,
>>> Krzysztof
>>>
>
next prev parent reply other threads:[~2023-04-06 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:40 [PATCH v2 0/5] soc: qcom: llcc: Add support for QDU1000/QRU1000 Komal Bajaj
2023-03-13 12:40 ` [PATCH v2 1/5] soc: qcom: llcc: Refactor llcc driver to support multiple configuration Komal Bajaj
2023-04-07 5:52 ` Abel Vesa
2023-03-13 12:40 ` [PATCH v2 2/5] dt-bindings: arm: msm: Add bindings for multi channel DDR in LLCC Komal Bajaj
2023-03-14 14:10 ` Rob Herring
2023-03-15 7:41 ` Krzysztof Kozlowski
2023-03-15 13:48 ` Manivannan Sadhasivam
[not found] ` <c8f3499f-d927-6657-c7c6-732ed2222525@quicinc.com>
2023-04-06 9:34 ` Krzysztof Kozlowski
2023-04-06 11:03 ` Mukesh Ojha
2023-04-06 9:52 ` Mukesh Ojha [this message]
2023-03-13 12:40 ` [PATCH v2 3/5] dt-bindings: arm: msm: Add LLCC compatible for QDU1000/QRU1000 Komal Bajaj
2023-03-13 12:40 ` [PATCH v2 4/5] soc: qcom: Add LLCC support for multi channel DDR Komal Bajaj
2023-03-14 23:23 ` kernel test robot
2023-03-15 7:34 ` Krzysztof Kozlowski
2023-03-15 14:08 ` Manivannan Sadhasivam
2023-03-13 12:40 ` [PATCH v2 5/5] soc: qcom: llcc: Add QDU1000 and QRU1000 LLCC support Komal Bajaj
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=d7d03e81-03d6-b643-a2e6-0867bab7e0ef@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_kbajaj@quicinc.com \
--cc=rishabhb@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=saiprakash.ranjan@codeaurora.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