From: Rob Herring <robh@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
kernel-team@android.com, Jay Chen <jkchen@linux.alibaba.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v1 0/2] perf/smmuv3: dts get opt and simplify code
Date: Mon, 13 Jul 2020 17:15:55 -0600 [thread overview]
Message-ID: <20200713231555.GA899100@bogus> (raw)
In-Reply-To: <159465365697.1899083.11140171455076785328.b4-ty@kernel.org>
On Mon, Jul 13, 2020 at 09:46:58PM +0100, Will Deacon wrote:
> On Mon, 6 Jul 2020 19:22:44 +0800, Jay Chen wrote:
> > This patch set firstly to simplify the code in smmu pmu probe,
> > and then support to get options in dts
> >
> > Jay Chen (2):
> > perf/smmuv3: To simplify code for ioremap page in pmcg
> > perf/smmuv3: To support the dts to get options
> >
> > [...]
>
> Applied to will (for-next/perf), thanks!
Without a binding document for the undocumented property and
compatible string!?
Is the 'arm-smmu-v3-pmcg' actually a separate block from the SMMU? Or is
this just an add a compatible to instantiate a driver?
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-13 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 11:22 [RFC PATCH v1 0/2] perf/smmuv3: dts get opt and simplify code Jay Chen
2020-07-06 11:22 ` [RFC PATCH v1 1/2] perf/smmuv3: To simplify code for ioremap page in pmcg Jay Chen
2020-07-06 11:22 ` [RFC PATCH v1 2/2] perf/smmuv3: To support the dts to get options Jay Chen
2020-07-06 15:03 ` Robin Murphy
2020-07-07 15:01 ` Jean-Philippe Brucker
2020-07-13 23:25 ` Rob Herring
2020-07-14 9:35 ` Robin Murphy
2020-07-13 20:46 ` [RFC PATCH v1 0/2] perf/smmuv3: dts get opt and simplify code Will Deacon
2020-07-13 23:15 ` Rob Herring [this message]
2020-07-14 7:48 ` Will Deacon
2020-07-14 7:49 ` Will Deacon
2020-07-14 22:26 ` Rob Herring
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=20200713231555.GA899100@bogus \
--to=robh@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jkchen@linux.alibaba.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@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).