From: chanho61.park@samsung.com (Chanho Park)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/3] ARM: EXYNOS: Enable PMUs for exynos4/5
Date: Sat, 28 Jul 2012 13:26:43 +0900 [thread overview]
Message-ID: <01c601cd6c79$30f508e0$92df1aa0$@samsung.com> (raw)
In-Reply-To: <20120727090201.GD559@mudshark.cambridge.arm.com>
> -----Original Message-----
> From: Will Deacon [mailto:will.deacon at arm.com]
> Sent: Friday, July 27, 2012 6:02 PM
> To: Chanho Park
> Cc: kgene.kim at samsung.com; linux-arm-kernel at lists.infradead.org; linux-
> samsung-soc at vger.kernel.org; sachin.kamat at linaro.org;
> linux at arm.linux.org.uk; Kyungmin Park
> Subject: Re: [PATCHv2 3/3] ARM: EXYNOS: Enable PMUs for exynos4/5
>
> On Fri, Jul 27, 2012 at 09:08:29AM +0100, Chanho Park wrote:
> > This patch define irq numbers of ARM performance monitoring unit for
> exynos4/5.
> > The number of CPU cores and PMU irq numbers are vary according to soc
> types.
> > So we need to identify each soc type using soc_is_xxx function and
> > define the pmu irqs dynamically. In case of exynos4412, there are 4 cpu
> cores and pmus.
>
> We have devicetree bindings for the PMU -- why can't you use those instead
> of probing the SoC all the time?
Hi Will,
Exynos4 isn't fully supported the DT yet. Thus, we should support legacy probing.
I'll support the DT for PMU after applied this patch.
Thank you
Best regards,
Chanho Park
>
> Will
next prev parent reply other threads:[~2012-07-28 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 8:08 [PATCHv2 0/3] Add support to enable ARM PMU for EXYNOS4/5 Chanho Park
2012-07-27 8:08 ` [PATCHv2 1/3] ARM: EXYNOS: Add set_irq_affinity function for combiner_irq Chanho Park
2012-07-27 8:08 ` [PATCHv2 2/3] ARM: EXYNOS: Correct combined IRQs for exynos4412 Chanho Park
2012-07-27 8:08 ` [PATCHv2 3/3] ARM: EXYNOS: Enable PMUs for exynos4/5 Chanho Park
2012-07-27 9:02 ` Will Deacon
2012-07-28 4:26 ` Chanho Park [this message]
2012-07-28 14:41 ` 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='01c601cd6c79$30f508e0$92df1aa0$@samsung.com' \
--to=chanho61.park@samsung.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).