All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Hu <nickhu@andestech.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "Greentime Ying-Han Hu(胡英漢)" <greentime@andestech.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"deanbo422@gmail.com" <deanbo422@gmail.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"Zong Zong-Xian Li(李宗憲)" <zong@andestech.com>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>
Subject: Re: [PATCH 5/5] nds32: Add document for NDS32 PMU.
Date: Mon, 22 Oct 2018 18:23:08 +0800	[thread overview]
Message-ID: <20181022102308.GD24110@andestech.com> (raw)
In-Reply-To: <20181018143132.vhhc6qpz4sooljlj@lakrids.cambridge.arm.com>

Hi Mark,

On Thu, Oct 18, 2018 at 10:31:32PM +0800, Mark Rutland wrote:
> On Thu, Oct 18, 2018 at 04:43:17PM +0800, Nickhu wrote:
> > The document for how to add NDS32 PMU
> > in devicetree.
> > 
> > Signed-off-by: Nickhu <nickhu@andestech.com>
> > ---
> >  Documentation/devicetree/bindings/nds32/pmu.txt | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/nds32/pmu.txt
> > 
> > diff --git a/Documentation/devicetree/bindings/nds32/pmu.txt b/Documentation/devicetree/bindings/nds32/pmu.txt
> > new file mode 100644
> > index 000000000000..02762b850e59
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nds32/pmu.txt
> > @@ -0,0 +1,17 @@
> > +* NDS32 Performance Monitor Units
> > +
> > +NDS32 core have a PMU for counting cpu and cache events like cache misses.
> > +The NDS32 PMU representation in the device tree should be done as under:
> > +
> > +Required properties:
> > +
> > +- compatilbe :
> > +	"andestech,atcpmu"
> 
> Which CPUs have this PMU?
> 
> I expected more specific strings, e.g. "andestech,n13-pmu" and/or
> "andestech,andestech,nds32v3-pmu".
>
In nds32 V3, all of our CPU have PMU.
So I will change the string to andestech,nds32v3-pmu.

> > +
> > +- interrupts : The interrupt number for NDS32 PMU is 13.
> > +
> > +Example:
> > +pmu{
> > +	compatible = "andestech,atcpmu";
> > +	interrupts = <13>;
> > +}
> 
> The driver tried to find multiple interrupts. Is there only a single
> interrupt in all cases?
> 
There is only overflow interrupt for performance couner in nds32 V3.
I will modified the driver and prepare another patch.
Thanks!

> Thanks,
> Mark.

Thank you for replying the patch set so quickly.
I will prepare the next patch set for it.
Thanks,
Nick

WARNING: multiple messages have this Message-ID (diff)
From: Nick Hu <nickhu@andestech.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "Greentime Ying-Han Hu(胡英漢)" <greentime@andestech.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"deanbo422@gmail.com" <deanbo422@gmail.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"acme@kernel.org" <acme@kernel.org>,
	"alexander.shishkin@linux.intel.com"
	<alexander.shishkin@linux.intel.com>,
	"jolsa@redhat.com" <jolsa@redhat.com>,
	"namhyung@kernel.org" <namhyung@kernel.org>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"sboyd@codeaurora.org" <sboyd@codeaurora.org>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"Zong Zong-Xian Li(李宗憲)" <zong@andestech.com>,
	"ebiederm@xmission.com" <ebiederm@xmission.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"pombredanne@nexb.com" <pombredanne@nexb.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"kstewart@linuxfoundation.org" <kstewart@linuxfoundation.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"green.hu@gmail.com" <green.hu@gmail.com>
Subject: Re: [PATCH 5/5] nds32: Add document for NDS32 PMU.
Date: Mon, 22 Oct 2018 18:23:08 +0800	[thread overview]
Message-ID: <20181022102308.GD24110@andestech.com> (raw)
In-Reply-To: <20181018143132.vhhc6qpz4sooljlj@lakrids.cambridge.arm.com>

Hi Mark,

On Thu, Oct 18, 2018 at 10:31:32PM +0800, Mark Rutland wrote:
> On Thu, Oct 18, 2018 at 04:43:17PM +0800, Nickhu wrote:
> > The document for how to add NDS32 PMU
> > in devicetree.
> > 
> > Signed-off-by: Nickhu <nickhu@andestech.com>
> > ---
> >  Documentation/devicetree/bindings/nds32/pmu.txt | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/nds32/pmu.txt
> > 
> > diff --git a/Documentation/devicetree/bindings/nds32/pmu.txt b/Documentation/devicetree/bindings/nds32/pmu.txt
> > new file mode 100644
> > index 000000000000..02762b850e59
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/nds32/pmu.txt
> > @@ -0,0 +1,17 @@
> > +* NDS32 Performance Monitor Units
> > +
> > +NDS32 core have a PMU for counting cpu and cache events like cache misses.
> > +The NDS32 PMU representation in the device tree should be done as under:
> > +
> > +Required properties:
> > +
> > +- compatilbe :
> > +	"andestech,atcpmu"
> 
> Which CPUs have this PMU?
> 
> I expected more specific strings, e.g. "andestech,n13-pmu" and/or
> "andestech,andestech,nds32v3-pmu".
>
In nds32 V3, all of our CPU have PMU.
So I will change the string to andestech,nds32v3-pmu.

> > +
> > +- interrupts : The interrupt number for NDS32 PMU is 13.
> > +
> > +Example:
> > +pmu{
> > +	compatible = "andestech,atcpmu";
> > +	interrupts = <13>;
> > +}
> 
> The driver tried to find multiple interrupts. Is there only a single
> interrupt in all cases?
> 
There is only overflow interrupt for performance couner in nds32 V3.
I will modified the driver and prepare another patch.
Thanks!

> Thanks,
> Mark.

Thank you for replying the patch set so quickly.
I will prepare the next patch set for it.
Thanks,
Nick

  reply	other threads:[~2018-10-22 10:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  8:43 [PATCH 0/5] nds32: Perf support Nickhu
2018-10-18  8:43 ` Nickhu
2018-10-18  8:43 ` [PATCH 1/5] nds32: Perf porting Nickhu
2018-10-18  8:43   ` Nickhu
2018-10-18 14:23   ` Mark Rutland
2018-10-22 10:18     ` Nick Hu
2018-10-22 10:18       ` Nick Hu
2018-10-22 13:15       ` Mark Rutland
2018-10-18  8:43 ` [PATCH 2/5] nds32: Fix bug in bitfield.h Nickhu
2018-10-18  8:43   ` Nickhu
2018-10-18 14:26   ` Mark Rutland
2018-10-22 10:19     ` Nick Hu
2018-10-22 10:19       ` Nick Hu
2018-10-18  8:43 ` [PATCH 3/5] nds32: Add perf call-graph support Nickhu
2018-10-18  8:43   ` Nickhu
2018-10-18  8:43 ` [PATCH 4/5] nds32: Fix perf multiple events map to same counter Nickhu
2018-10-18  8:43   ` Nickhu
2018-10-18 14:29   ` Mark Rutland
2018-10-22 10:20     ` Nick Hu
2018-10-22 10:20       ` Nick Hu
2018-10-18  8:43 ` [PATCH 5/5] nds32: Add document for NDS32 PMU Nickhu
2018-10-18  8:43   ` Nickhu
2018-10-18 14:31   ` Mark Rutland
2018-10-22 10:23     ` Nick Hu [this message]
2018-10-22 10:23       ` Nick Hu
2018-10-22 13:17       ` Mark Rutland
2018-10-22 13:17         ` Mark Rutland

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=20181022102308.GD24110@andestech.com \
    --to=nickhu@andestech.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=deanbo422@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=geert@linux-m68k.org \
    --cc=greentime@andestech.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@codeaurora.org \
    --cc=zong@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.