From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Frank Li <Frank.Li@kernel.org>, Andy Gross <agross@kernel.org>,
Harshal Dev <harshal.dev@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: dma: qcom,bam-dma: Increase iommus maxItems to seven
Date: Mon, 8 Jun 2026 21:49:00 +0200 [thread overview]
Message-ID: <844eccf8-4ad3-46a2-bc8a-67895d629c4f@kernel.org> (raw)
In-Reply-To: <289a5bca-5491-4fc2-92d9-1102aa664021@oss.qualcomm.com>
On 06/06/2026 22:59, Kuldeep Singh wrote:
> On 30-05-2026 16:09, Krzysztof Kozlowski wrote:
>> On Thu, May 21, 2026 at 06:47:11PM +0530, Kuldeep Singh wrote:
>>> Shikra bam dma engine support 7 iommu entries and not 6.
>>> Increase maxItems property for iommus to pass dtbs_check errors.
>>
>> What errors? There is no Shikra in upstream so how could we have errors?
> dt-bindings updates are prerequisites for the DT changes of ice,rng, qce
> and hence updated bindings in patch [1-4]/5.
> Also, the commit message mention about shikra and DT change is also in
> same series.
>
> I hope this clarifies.
No, nothing is clarified. This commit msg is just misleading.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-08 19:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 13:17 [PATCH 0/5] Shikra: Add DT support for ice, rng and qce Kuldeep Singh
2026-05-21 13:17 ` [PATCH 1/5] dt-bindings: crypto: qcom,inline-crypto-engine: Document Shikra ICE Kuldeep Singh
2026-05-30 10:38 ` Krzysztof Kozlowski
2026-06-06 20:56 ` Kuldeep Singh
2026-05-21 13:17 ` [PATCH 2/5] dt-bindings: crypto: qcom,prng: Document Shikra TRNG Kuldeep Singh
2026-05-21 13:17 ` [PATCH 3/5] dt-bindings: crypto: qcom-qce: Document the Shikra crypto engine Kuldeep Singh
2026-05-21 13:17 ` [PATCH 4/5] dt-bindings: dma: qcom,bam-dma: Increase iommus maxItems to seven Kuldeep Singh
2026-05-30 10:39 ` Krzysztof Kozlowski
2026-06-06 20:59 ` Kuldeep Singh
2026-06-07 8:13 ` Krzysztof Kozlowski
2026-06-08 18:43 ` Kuldeep Singh
2026-06-08 19:49 ` Krzysztof Kozlowski [this message]
2026-06-09 5:37 ` Kuldeep Singh
2026-06-09 6:24 ` Krzysztof Kozlowski
2026-05-21 13:17 ` [PATCH 5/5] arm64: dts: qcom: shikra: Add ICE, TRNG and QCE nodes Kuldeep Singh
2026-06-07 10:13 ` Dmitry Baryshkov
2026-06-08 10:09 ` Kuldeep Singh
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=844eccf8-4ad3-46a2-bc8a-67895d629c4f@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=harshal.dev@oss.qualcomm.com \
--cc=herbert@gondor.apana.org.au \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thara.gopinath@gmail.com \
--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