Thread (20 messages) 20 messages, 3 authors, 2017-05-18

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

From: Leo Yan <hidden>
Date: 2017-05-12 00:10:36
Also in: linux-arm-kernel, linux-arm-msm, lkml

On Thu, May 11, 2017 at 11:12:32AM -0600, Mathieu Poirier wrote:

[...]
quoted
+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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help