From: Richard Acayan <mailingradian@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
Richard Acayan <mailingradian@gmail.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: dma: qcom: gpi: add fallback
Date: Fri, 23 Sep 2022 18:20:28 -0400 [thread overview]
Message-ID: <20220923222028.284561-1-mailingradian@gmail.com> (raw)
In-Reply-To: <7b066e11-6e5c-c6d9-c8ed-9feccaec4c0c@linaro.org>
> On 23/09/2022 23:09, Richard Acayan wrote:
> > The drivers are transitioning from matching against lists of specific
> > compatible strings to matching against smaller lists of more generic
> > compatible strings. Add a fallback compatible string in the schema to
> > support this change.
>
> Thanks for the patch. I wished we discussed it a bit more. :)
Ah, sorry for not replying to your original suggestion. I didn't see the
opportunity for discussion as this new series wasn't that hard to come up
with.
> qcom,gpi-dma does not look like specific enough to be correct fallback,
> at least not for all of the devices. I propose either a IP block version
> (which is tricky without access to documentation) or just one of the SoC
> IP blocks.
Solution 1:
Yes, I could use something like qcom,sdm845-gpi-dma. It would be weird to
see the compatible strings for that, though:
compatible = "qcom,sdm670-gpi-dma", "qcom,sdm845-gpi-dma";
// This would need to be valid in dt schema, suggesting solution 2
compatible = "qcom,sdm845-gpi-dma";
// This just doesn't make sense
compatible = "qcom,sdm845-gpi-dma", "qcom,sdm845-gpi-dma";
compatible = "qcom,sm8150-gpi-dma", "qcom,sdm845-gpi-dma";
compatible = "qcom,sm8250-gpi-dma", "qcom,sdm845-gpi-dma";
Solution 2:
I could stray from the "soc-specific compat", "fallback compat" and just
have "qcom,sdm845-gpi-dma" for every SoC.
Solution 3:
I found the original mailing list archive for this driver:
https://lore.kernel.org/linux-arm-msm/20200824084712.2526079-1-vkoul@kernel.org/
https://lore.kernel.org/linux-arm-msm/20200918062955.2095156-1-vkoul@kernel.org/
It seems like the author originally handled the ee_offset as a dt property
and removed it. It was removed because it was a Qualcomm-specific property.
One option would be to bring this back against the author's wishes (or ask
the author about it, since they are a recipient).
Solution 4:
You mentioned there being an xPU3 block here:
https://lore.kernel.org/linux-arm-msm/e3bfa28a-ecbc-7a57-a996-042650043514@linaro.org/
Maybe it's fine to have qcom,gpi-dma-v3?
next prev parent reply other threads:[~2022-09-23 22:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 21:09 [PATCH v2 0/4] SDM670 GPI DMA support Richard Acayan
2022-09-23 21:09 ` [PATCH v2 1/4] dt-bindings: dma: qcom: gpi: add fallback compatible Richard Acayan
2022-09-23 21:26 ` Krzysztof Kozlowski
2022-09-23 22:20 ` Richard Acayan [this message]
2022-09-26 23:12 ` [PATCH v2 1/4] dt-bindings: dma: qcom: gpi: add fallback Rob Herring
2022-09-27 1:53 ` Richard Acayan
2022-09-28 7:57 ` Krzysztof Kozlowski
2022-09-29 7:39 ` [PATCH v2 1/4] dt-bindings: dma: qcom: gpi: add fallback compatible Vinod Koul
2022-09-29 7:47 ` Krzysztof Kozlowski
2022-09-23 21:09 ` [PATCH v2 2/4] dt-bindings: dma: qcom: gpi: add compatible for sdm670 Richard Acayan
2022-09-23 21:09 ` [PATCH v2 3/4] arm64: dts: qcom: add gpi-dma fallback compatible Richard Acayan
2022-09-23 21:09 ` [PATCH v2 4/4] dmaengine: qcom: gpi: drop redundant of_device_id entries Richard Acayan
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=20220923222028.284561-1-mailingradian@gmail.com \
--to=mailingradian@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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