linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dhdang@apm.com (Duc Dang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver
Date: Wed, 20 Jul 2016 11:04:42 -0700	[thread overview]
Message-ID: <CADaLND=5Wu6+2G2E1K28BejGenRi89yODACdwhZJVr-Ee+um6w@mail.gmail.com> (raw)
In-Reply-To: <20160720101553.GA20508@arm.com>

On Wed, Jul 20, 2016 at 3:15 AM, Will Deacon <will.deacon@arm.com> wrote:
> On Tue, Jul 19, 2016 at 01:22:09PM -0700, Duc Dang wrote:
>> On Thu, Jul 14, 2016 at 10:37 AM, Duc Dang <dhdang@apm.com> wrote:
>> > On Thu, Jul 14, 2016 at 10:28 AM, Tai Tri Nguyen <ttnguyen@apm.com> wrote:
>> >> On Thu, Jul 14, 2016 at 6:16 AM, Will Deacon <will.deacon@arm.com> wrote:
>> >> > On Mon, Jul 11, 2016 at 12:05:40PM -0700, Tai Nguyen wrote:
>> >> >> In addition to the X-Gene ARM CPU performance monitoring unit (PMU), there
>> >> >> are PMU for the SoC system devices such as L3 cache(s), I/O bridge(s),
>> >> >> memory controller bridges and memory. These PMU devices are loosely
>> >> >> architected to follow the same model as the PMU for ARM cores.
>> >> >
>> >> > You might want to add commit messages to patches 1,2 and 4, but then you
>> >> > can route this via the arm-soc tree.
>> >> >
>> >> > Will
>> >>
>> >> I will add the commit messages to these patches 1, 2 and 4 and rout
>> >> this via arm-soc tree.
>> >> CC: Duc (dhdang at apm.com)
>> >
>> > I will pull patch 1, 2 and 4 into xgene-next tree and send pull
>> > request to Arnd and Olof.
>>
>> Hi Will,
>>
>> Do you plan to merge this series (Tai posted v10) into 4.8 or you want
>> to wait until 4.9? Please let know so that I can plan my pull request
>> to Arnd/Olof accordingly to include patch 1, 2, and 4.
>
> I was hoping that the whole series would go via arm-soc. Mark reviewed
> the PMU driver code, so that should be sufficient.

Thanks, Will.

Hi Arnd, Olof,

Can you please help merge v10 of this series into your arm-soc tree? I
can merge this series into xgene-next and send a pull request to you
too, but the pull request will only contain this series as I don't
have more dts changes at this time.

Regards,
Duc Dang.
>
> Will

      reply	other threads:[~2016-07-20 18:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 19:05 [PATCH v8 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-07-11 19:05 ` [PATCH v8 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver Tai Nguyen
2016-07-11 19:05 ` [PATCH v8 2/4] Documentation: Add documentation for APM X-Gene SoC PMU DTS binding Tai Nguyen
2016-07-11 19:05 ` [PATCH v8 3/4] perf: xgene: Add APM X-Gene SoC Performance Monitoring Unit driver Tai Nguyen
2016-07-11 19:05 ` [PATCH v8 4/4] arm64: dts: apm: Add APM X-Gene SoC PMU DTS entries Tai Nguyen
2016-07-14 13:16 ` [PATCH v8 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver Will Deacon
2016-07-14 17:28   ` Tai Tri Nguyen
2016-07-14 17:37     ` Duc Dang
2016-07-19 20:22       ` Duc Dang
2016-07-20 10:15         ` Will Deacon
2016-07-20 18:04           ` Duc Dang [this message]

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='CADaLND=5Wu6+2G2E1K28BejGenRi89yODACdwhZJVr-Ee+um6w@mail.gmail.com' \
    --to=dhdang@apm.com \
    --cc=linux-arm-kernel@lists.infradead.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).