From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Will Deacon <will@kernel.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Jonathan Marek <jonathan@marek.ca>,
linux-arm-msm@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
"open list:IOMMU DRIVERS" <iommu@lists.linux-foundation.org>,
Andy Gross <agross@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"moderated list:ARM SMMU DRIVERS"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/8] arm64: dts: qcom: smmu/USB nodes and HDK855/HDK865 dts
Date: Wed, 8 Jul 2020 21:44:20 -0700 [thread overview]
Message-ID: <20200709044420.GB3453565@ripper> (raw)
In-Reply-To: <20200703123113.GA18953@willie-the-truck>
On Fri 03 Jul 05:31 PDT 2020, Will Deacon wrote:
> On Tue, Jun 09, 2020 at 03:40:18PM -0400, Jonathan Marek wrote:
> > Add dts nodes for apps_smmu and USB for both sm8150 and sm8250.
> >
> > Also add initial dts files for HDK855 and HDK865, based on mtp dts, with a
> > few changes. Notably, the HDK865 dts has regulator config changed a bit based
> > on downstream (I think sm8250-mtp.dts is wrong and copied too much from sm8150).
> >
> > V2 changes:
> > * Added two patches for sm8150 and sm8250 iommu compatibles
> > * Changed apps_smmu node patches to use new compatibles
> > * Updated commit messages for apps_smmu patches to be more correct
> > * Updated HDK dts patches based on Bjorn's comments
> >
> > Jonathan Marek (8):
> > dt-bindings: arm-smmu: Add sm8150 and sm8250 compatible strings
> > iommu: arm-smmu-impl: Use qcom impl for sm8150 and sm8250 compatibles
> > arm64: dts: qcom: sm8150: add apps_smmu node
> > arm64: dts: qcom: sm8250: add apps_smmu node
> > arm64: dts: qcom: sm8150: Add secondary USB and PHY nodes
> > arm64: dts: qcom: sm8250: Add USB and PHY device nodes
> > arm64: dts: qcom: add sm8150 hdk dts
> > arm64: dts: qcom: add sm8250 hdk dts
>
> What's your plan for merging this? I can take the first two patches
> via arm-smmu, if you like. Please just let me know.
>
Please pick up the binding and driver patch through your tree.
Regards,
Bjorn
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-07-09 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 19:40 [PATCH v2 0/8] arm64: dts: qcom: smmu/USB nodes and HDK855/HDK865 dts Jonathan Marek
2020-06-09 19:40 ` [PATCH v2 1/8] dt-bindings: arm-smmu: Add sm8150 and sm8250 compatible strings Jonathan Marek
2020-06-17 22:05 ` Rob Herring
2020-06-09 19:40 ` [PATCH v2 2/8] iommu: arm-smmu-impl: Use qcom impl for sm8150 and sm8250 compatibles Jonathan Marek
2020-06-18 16:56 ` Robin Murphy
2020-07-09 4:43 ` Bjorn Andersson
2020-07-03 12:31 ` [PATCH v2 0/8] arm64: dts: qcom: smmu/USB nodes and HDK855/HDK865 dts Will Deacon
2020-07-09 4:44 ` Bjorn Andersson [this message]
2020-07-09 9:54 ` Will Deacon
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=20200709044420.GB3453565@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathan@marek.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).