From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 7/9] coresight: add support for CPU debug module
Date: Fri, 12 May 2017 08:10:11 +0800 [thread overview]
Message-ID: <20170512001010.GA13845@leoy-ThinkPad-T440> (raw)
In-Reply-To: <20170511171232.GA21765@linaro.org>
On Thu, May 11, 2017 at 11:12:32AM -0600, Mathieu Poirier wrote:
[...]
> > +static int debug_probe(struct amba_device *adev, const struct amba_id *id)
> > +{
> > + void __iomem *base;
> > + struct device *dev = &adev->dev;
> > + struct debug_drvdata *drvdata;
> > + struct resource *res = &adev->res;
> > + struct device_node *np = adev->dev.of_node;
> > + int ret;
> > +
> > + drvdata = devm_kzalloc(dev, sizeof(*drvdata), GFP_KERNEL);
> > + if (!drvdata)
> > + return -ENOMEM;
> > +
> > + drvdata->cpu = np ? of_coresight_get_cpu(np) : 0;
> > + if (per_cpu(debug_drvdata, drvdata->cpu)) {
> > + dev_err(dev, "CPU%d drvdata has been initialized, "
>
> s/"has been"/"has already been"
>
> That way it really look like an error message.
Will fix.
> Also debug_probe() uses dev_xyz() but everywhere else in the driver it is
> pr_xyz() - any specific reason for that? I suggest moving to dev_xyz().
Some logs are shared for all device instances, so I think should use
pr_xyz(); will spin a new version to change other places to use
dev_xyz() if the logs are for specific device instance.
> Otherwise things look good.
[...]
Thanks,
Leo Yan
next prev parent reply other threads:[~2017-05-12 0:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 2:49 [PATCH v9 0/9] coresight: enable debug module Leo Yan
2017-05-09 2:49 ` [PATCH v9 1/9] coresight: bindings for CPU " Leo Yan
2017-05-09 2:49 ` [PATCH v9 2/9] doc: Add documentation for Coresight CPU debug Leo Yan
2017-05-11 17:19 ` Mathieu Poirier
2017-05-09 2:49 ` [PATCH v9 3/9] doc: Add coresight_cpu_debug.enable to kernel-parameters.txt Leo Yan
2017-05-11 17:20 ` Mathieu Poirier
2017-05-09 2:49 ` [PATCH v9 4/9] MAINTAINERS: update file entries for Coresight subsystem Leo Yan
2017-05-11 17:21 ` Mathieu Poirier
2017-05-09 2:49 ` [PATCH v9 5/9] coresight: of_get_coresight_platform_data: Add missing of_node_put Leo Yan
2017-05-09 2:49 ` [PATCH v9 6/9] coresight: refactor with function of_coresight_get_cpu Leo Yan
2017-05-09 2:50 ` [PATCH v9 7/9] coresight: add support for CPU debug module Leo Yan
2017-05-11 17:12 ` Mathieu Poirier
2017-05-12 0:10 ` Leo Yan [this message]
2017-05-11 17:40 ` Suzuki K Poulose
2017-05-09 2:50 ` [PATCH v9 8/9] arm64: dts: hi6220: register " Leo Yan
2017-05-11 17:16 ` Mathieu Poirier
2017-05-09 2:50 ` [PATCH v9 9/9] arm64: dts: qcom: msm8916: Add debug unit Leo Yan
2017-05-11 17:18 ` Mathieu Poirier
2017-05-18 12:59 ` [PATCH v9 0/9] coresight: enable debug module Suzuki K Poulose
2017-05-18 13:04 ` 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=20170512001010.GA13845@leoy-ThinkPad-T440 \
--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