From: Will Deacon <will@kernel.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>
Cc: "mark.rutland@arm.com" <mark.rutland@arm.com>,
Frank Li <frank.li@nxp.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 3/4] perf/imx_ddr: Add enhanced AXI ID filter support
Date: Thu, 31 Oct 2019 15:38:58 +0000 [thread overview]
Message-ID: <20191031153858.GA28061@willie-the-truck> (raw)
In-Reply-To: <20191029070314.16719-3-qiangqing.zhang@nxp.com>
On Tue, Oct 29, 2019 at 07:06:19AM +0000, Joakim Zhang wrote:
> With DDR_CAP_AXI_ID_FILTER quirk, indicating HW supports AXI ID filter
> which only can get bursts from DDR transaction, i.e. DDR read/write
> requests.
>
> This patch add DDR_CAP_AXI_ID_ENHANCED_FILTER quirk, indicating HW
> supports AXI ID filter which can get bursts and bytes from DDR
> transaction at the same time. We hope PMU always return bytes in the
> driver due to it is more meaningful for users.
>
> DDR_CAP_AXI_ID_ENHANCED_FILTER is based on DDR_CAP_AXI_ID_FILTER and
> extend it a bit. So need select both above two qiurks together when
> HW supports enhanced AXI ID filter.
>
> Signed-off-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> ---
> Changelog:
> V1->V2:
> * use ddr_perf_is_filtered() helper to simply the code.
> * improve the commit message.
> ---
> drivers/perf/fsl_imx8_ddr_perf.c | 55 ++++++++++++++++++++------------
> 1 file changed, 34 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/perf/fsl_imx8_ddr_perf.c b/drivers/perf/fsl_imx8_ddr_perf.c
> index ce7345745b42..17c817d89222 100644
> --- a/drivers/perf/fsl_imx8_ddr_perf.c
> +++ b/drivers/perf/fsl_imx8_ddr_perf.c
> @@ -45,7 +45,8 @@
> static DEFINE_IDA(ddr_ida);
>
> /* DDR Perf hardware feature */
> -#define DDR_CAP_AXI_ID_FILTER 0x1 /* support AXI ID filter */
> +#define DDR_CAP_AXI_ID_FILTER BIT(1) /* support AXI ID filter */
> +#define DDR_CAP_AXI_ID_FILTER_ENHANCED BIT(2) /* support enhanced AXI ID filter */
I still don't understand why you don't do something like this:
#define DDR_CAP_AXI_ID_FILTER 0x1 /* support AXI ID filter */
#define DDR_CAP_AXI_ID_FILTER_ENHANCED 0x3 /* support enhanced AXI ID filter */
static bool ddr_perf_is_enhanced_filtered(struct perf_event *event)
{
unsigned int filt;
struct ddr_pmu *pmu = to_ddr_pmu(event->pmu);
filt = pmu->devtype_data->quirks & DDR_CAP_AXI_ID_FILTER_ENHANCED;
return (filt == DDR_CAP_AXI_ID_FILTER_ENHANCED) &&
ddr_perf_is_filtered(event);
}
and then:
> + /*
> + * return bytes instead of bursts from ddr transaction for
> + * axid-read and axid-write event if PMU core supports enhanced
> + * filter.
> + */
> + if ((pmu->devtype_data->quirks & DDR_CAP_AXI_ID_FILTER) &&
> + (pmu->devtype_data->quirks & DDR_CAP_AXI_ID_FILTER_ENHANCED) &&
> + ddr_perf_is_filtered(event)) {
static u32 ddr_perf_read_counter(struct ddr_pmu *pmu, int counter)
{
struct perf_event *event = pmu->events[counter];
void __iomem *base = pmu->base;
base += ddr_perf_is_enhanced_filtered(event) ? COUNTER_DPCR1 :
COUNTER_READ;
return readl_relaxed(base + counter * 4);
}
In patch 4 you can then do:
.quirks = DDR_CAP_AXI_ID_FILTER_ENHANCED;
Make sense?
Will
_______________________________________________
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:[~2019-10-31 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 7:06 [PATCH V2 1/4] docs/perf: Add explanation for DDR_CAP_AXI_ID_FILTER_ENHANCED quirk Joakim Zhang
2019-10-29 7:06 ` [PATCH V2 2/4] bindings: perf: imx-ddr: Add new compatible string Joakim Zhang
2019-10-29 7:06 ` [PATCH V2 3/4] perf/imx_ddr: Add enhanced AXI ID filter support Joakim Zhang
2019-10-31 15:38 ` Will Deacon [this message]
2019-11-01 8:21 ` Joakim Zhang
2019-10-29 7:06 ` [PATCH V2 4/4] perf/imx_ddr: Add driver for DDR PMU in i.MX8MPlus Joakim Zhang
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=20191031153858.GA28061@willie-the-truck \
--to=will@kernel.org \
--cc=frank.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=qiangqing.zhang@nxp.com \
--cc=robin.murphy@arm.com \
/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