From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 6/9] coresight: add support for CPU debug module
Date: Wed, 29 Mar 2017 18:37:12 +0800 [thread overview]
Message-ID: <20170329103712.GA22480@leoy-linaro> (raw)
In-Reply-To: <89b6c6c7-0da0-6891-312a-c9221851c20a@arm.com>
On Wed, Mar 29, 2017 at 11:31:03AM +0100, Suzuki K Poulose wrote:
> On 29/03/17 11:27, Leo Yan wrote:
> >On Wed, Mar 29, 2017 at 10:07:07AM +0100, Suzuki K Poulose wrote:
> >
> >[...]
> >
> >>>>>+ if (mode == EDDEVID_IMPL_NONE) {
> >>>>>+ drvdata->edpcsr_present = false;
> >>>>>+ drvdata->edcidsr_present = false;
> >>>>>+ drvdata->edvidsr_present = false;
> >>>>>+ } else if (mode == EDDEVID_IMPL_EDPCSR) {
> >>>>>+ drvdata->edpcsr_present = true;
> >>>>>+ drvdata->edcidsr_present = false;
> >>>>>+ drvdata->edvidsr_present = false;
> >>>>>+ } else if (mode == EDDEVID_IMPL_EDPCSR_EDCIDSR) {
> >>>>>+ if (!IS_ENABLED(CONFIG_64BIT) &&
> >>>>>+ (pcsr_offset == EDDEVID1_PCSR_NO_OFFSET_DIS_AARCH32))
> >>>>>+ drvdata->edpcsr_present = false;
> >>>>>+ else
> >>>>>+ drvdata->edpcsr_present = true;
> >>>>
> >>>>Sorry, I forgot why we do this check only in this mode. Shouldn't this be
> >>>>common to all modes (of course which implies PCSR is present) ?
> >>>
> >>>No. PCSROffset is defined differently in ARMv7 and ARMv8; So finally we
> >>>simplize PCSROffset value :
> >>>0000 - Sample offset applies based on the instruction state (indicated by PCSR[0])
> >>>0001 - No offset applies.
> >>>0010 - No offset applies, but do not use in AArch32 mode!
> >>>
> >>>So we need handle the corner case is when CPU runs AArch32 mode and
> >>>PCSRoffset = 'b0010. Other cases the pcsr should be present.
> >>
> >>I understand that reasoning. But my question is, why do we check for PCSROffset
> >>only when mode == EDDEVID_IMPL_EDPCSR_EDCIDSR and not for say mode == EDDEVID_IMPL_EDPCSR or
> >>any other mode where PCSR is present.
> >
> >Sorry I misunderstood your question.
> >
> >I made mistake when I analyzed the possbile combination for mode and
> >PCSROffset so I thought it's the only case should handle:
> >{ EDDEVID_IMPL_EDPCSR_EDCIDSR, EDDEVID1_PCSR_NO_OFFSET_DIS_AARCH32 }
> >
> >Below three combinations are possible to exist; so you are right, I
> >should move this out for the checking:
> >{ EDDEVID_IMPL_NONE, EDDEVID1_PCSR_NO_OFFSET_DIS_AARCH32 }
>
> That need not be covered, as IMPL_NONE says PCSR is not implemented hence you
> don't worry about anything as the functionality is missing. This should rather be:
> EDDEVID_IMPL_EDPCSR, where only PCSR is implemented.
I think below combination doesn't really exist:
{ EDDEVID_IMPL_EDPCSR, EDDEVID1_PCSR_NO_OFFSET_DIS_AARCH32 };
EDDEVID_IMPL_EDPCSR is only defined in ARMv7 ARM, and
EDDEVID1_PCSR_NO_OFFSET_DIS_AARCH32 is only defined in ARMv8 ARM.
> My switch...case suggestion makes it easier to do all this checking.
Agree. Will do this.
Thanks,
Leo Yan
next prev parent reply other threads:[~2017-03-29 10:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-25 18:23 [PATCH v5 0/9] coresight: enable debug module Leo Yan
2017-03-25 18:23 ` [PATCH v5 1/9] coresight: bindings for CPU " Leo Yan
2017-03-30 22:49 ` Rob Herring
2017-03-31 9:04 ` Suzuki K Poulose
2017-03-25 18:23 ` [PATCH v5 2/9] doc: Add documentation for Coresight CPU debug Leo Yan
2017-03-25 18:23 ` [PATCH v5 3/9] coresight: of_get_coresight_platform_data: Add missing of_node_put Leo Yan
2017-03-25 18:23 ` [PATCH v5 4/9] coresight: refactor with function of_coresight_get_cpu Leo Yan
2017-03-31 9:05 ` Suzuki K Poulose
2017-03-25 18:23 ` [PATCH v5 5/9] coresight: use const for device_node structures Leo Yan
2017-04-04 21:48 ` Stephen Boyd
2017-03-25 18:23 ` [PATCH v5 6/9] coresight: add support for CPU debug module Leo Yan
2017-03-27 16:34 ` Suzuki K Poulose
2017-03-29 3:07 ` Leo Yan
2017-03-29 9:07 ` Suzuki K Poulose
2017-03-29 10:27 ` Leo Yan
2017-03-29 10:31 ` Suzuki K Poulose
2017-03-29 10:37 ` Leo Yan [this message]
2017-03-29 15:50 ` Suzuki K Poulose
2017-03-29 15:17 ` Mike Leach
2017-03-30 1:18 ` Leo Yan
2017-03-29 15:41 ` Mathieu Poirier
2017-03-28 16:50 ` Mathieu Poirier
2017-03-29 1:54 ` Leo Yan
2017-03-29 14:56 ` Mike Leach
2017-03-30 1:03 ` Leo Yan
2017-03-30 9:00 ` Suzuki K Poulose
2017-03-30 13:51 ` Leo Yan
2017-03-30 15:47 ` Sudeep Holla
2017-03-29 16:55 ` Mathieu Poirier
2017-03-30 1:59 ` Leo Yan
2017-03-30 15:46 ` Mathieu Poirier
2017-03-30 16:04 ` Sudeep Holla
2017-03-30 15:56 ` Sudeep Holla
2017-03-31 0:54 ` Leo Yan
2017-03-25 18:23 ` [PATCH v5 7/9] clk: hi6220: add debug APB clock Leo Yan
2017-04-04 21:51 ` Stephen Boyd
2017-04-06 13:59 ` Leo Yan
2017-03-25 18:23 ` [PATCH v5 8/9] arm64: dts: hi6220: register debug module Leo Yan
2017-03-25 18:23 ` [PATCH v5 9/9] arm64: dts: qcom: msm8916: Add debug unit Leo Yan
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=20170329103712.GA22480@leoy-linaro \
--to=leo.yan@linaro.org \
--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).