From: Hao Zhang <quic_hazha@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>, Leo Yan <leo.yan@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Konrad Dybcio <konradybcio@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andy Gross <agross@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Jonathan Corbet <corbet@lwn.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Tingwei Zhang <quic_tingweiz@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>,
"Yuanfang Zhang" <quic_yuanfang@quicinc.com>,
Tao Zhang <quic_taozha@quicinc.com>,
Trilok Soni <quic_tsoni@quicinc.com>,
<linux-arm-msm@vger.kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
<linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] Coresight: Add coresight dummy driver
Date: Wed, 24 May 2023 14:12:30 +0800 [thread overview]
Message-ID: <0be9ea3f-d48c-c475-8081-b80cf2cd50dd@quicinc.com> (raw)
In-Reply-To: <c815d436-85aa-be07-e224-4d5d042c847d@quicinc.com>
On 5/10/2023 10:56 AM, Hao Zhang wrote:
> Hi Suzuki,
>
> On 5/5/2023 5:57 PM, Suzuki K Poulose wrote:
>> On 05/05/2023 10:24, Hao Zhang wrote:
>>> Some Coresight devices that kernel don't have permission to access or
>>> configure. So there need driver to register dummy devices as Coresight
>>> devices. It may also be used to define components that may not have
>>> any programming interfaces (e.g, static links), so that paths can be
>>> established in the driver. Provide Coresight API for dummy device
>>> operations, such as enabling and disabling dummy devices. Build the
>>> Coresight path for dummy sink or dummy source for debugging.
>>>
>>> Signed-off-by: Hao Zhang <quic_hazha@quicinc.com>
>>> ---
>>> drivers/hwtracing/coresight/Kconfig | 11 ++
>>> drivers/hwtracing/coresight/Makefile | 1 +
>>> drivers/hwtracing/coresight/coresight-dummy.c | 171 ++++++++++++++++++
>>> include/linux/coresight.h | 1 +
>>> 4 files changed, 184 insertions(+)
>>> create mode 100644 drivers/hwtracing/coresight/coresight-dummy.c
>>>
>>> diff --git a/drivers/hwtracing/coresight/Kconfig
>>> b/drivers/hwtracing/coresight/Kconfig
>>> index 2b5bbfffbc4f..06f0a7594169 100644
>>> --- a/drivers/hwtracing/coresight/Kconfig
>>> +++ b/drivers/hwtracing/coresight/Kconfig
>>> @@ -236,4 +236,15 @@ config CORESIGHT_TPDA
>>> To compile this driver as a module, choose M here: the module
>>> will be
>>> called coresight-tpda.
>>> +
>>> +config CORESIGHT_DUMMY
>>> + tristate "Dummy driver support"
>>> + help
>>> + Enables support for dummy driver. Dummy driver can be used for
>>> + CoreSight sources/sinks that are owned and configured by some
>>> + other subsystem and use Linux drivers to configure rest of trace
>>> + path > +
>>> + To compile this driver as a module, choose M here: the module
>>> will be
>>> + called coresight-dummy.
>>> endif
>>> diff --git a/drivers/hwtracing/coresight/Makefile
>>> b/drivers/hwtracing/coresight/Makefile
>>> index 33bcc3f7b8ae..995d3b2c76df 100644
>>> --- a/drivers/hwtracing/coresight/Makefile
>>> +++ b/drivers/hwtracing/coresight/Makefile
>>> @@ -30,3 +30,4 @@ obj-$(CONFIG_CORESIGHT_TPDA) += coresight-tpda.o
>>> coresight-cti-y := coresight-cti-core.o coresight-cti-platform.o \
>>> coresight-cti-sysfs.o
>>> obj-$(CONFIG_ULTRASOC_SMB) += ultrasoc-smb.o
>>> +obj-$(CONFIG_CORESIGHT_DUMMY) += coresight-dummy.o
>>> diff --git a/drivers/hwtracing/coresight/coresight-dummy.c
>>> b/drivers/hwtracing/coresight/coresight-dummy.c
>>> new file mode 100644
>>> index 000000000000..ee9881ff4754
>>> --- /dev/null
>>> +++ b/drivers/hwtracing/coresight/coresight-dummy.c
>>> @@ -0,0 +1,171 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/*
>>> + * Copyright (c) 2023 Qualcomm Innovation Center, Inc. All rights
>>> reserved.
>>> + */
>>> +
>>> +#include <linux/kernel.h>
>>> +#include <linux/module.h>
>>> +#include <linux/platform_device.h>
>>> +#include <linux/coresight.h>
>>> +#include <linux/of.h>
>>> +#include <linux/pm_runtime.h>
>>
>> Please follow the alphabetical order for the header files ^
>>
> Sure, I will update this in the next patch series.
>
>>> +
>>> +#include "coresight-priv.h"
>>> +
>>> +struct dummy_drvdata {
>>> + struct device *dev;
>>
>> nit: We don't need this really. And that completely removes the need for
>> drvdata too. See below.
>>
>>> + struct coresight_device *csdev;
>>> +};
>>> +
>>> +DEFINE_CORESIGHT_DEVLIST(source_devs, "dummy_source");
>>> +DEFINE_CORESIGHT_DEVLIST(sink_devs, "dummy_sink");
>>> +
>>> +static int dummy_source_enable(struct coresight_device *csdev,
>>> + struct perf_event *event, u32 mode)
>>> +{
>>> + struct dummy_drvdata *drvdata = dev_get_drvdata(csdev->dev.parent);
>>> +
>>> + dev_dbg(drvdata->dev, "Dummy source enabled\n");
>>
>> dev_dbg(csdev->dev.parent, ..");
>>
>> Similarly for all instances below.
>>
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static void dummy_source_disable(struct coresight_device *csdev,
>>> + struct perf_event *event)
>>> +{
>>> + struct dummy_drvdata *drvdata = dev_get_drvdata(csdev->dev.parent);
>>> +
>>> + dev_dbg(drvdata->dev, "Dummy source disabled\n");
>>> +}
>>> +
>>> +static int dummy_sink_enable(struct coresight_device *csdev, u32 mode,
>>> + void *data)
>>> +{
>>> + struct dummy_drvdata *drvdata = dev_get_drvdata(csdev->dev.parent);
>>> +
>>> + dev_dbg(drvdata->dev, "Dummy sink enabled\n");
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static int dummy_sink_disable(struct coresight_device *csdev)
>>> +{
>>> + struct dummy_drvdata *drvdata = dev_get_drvdata(csdev->dev.parent);
>>> +
>>> + dev_dbg(drvdata->dev, "Dummy sink disabled\n");
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +static const struct coresight_ops_source dummy_source_ops = {
>>> + .enable = dummy_source_enable,
>>> + .disable = dummy_source_disable,
>>> +};
>>> +
>>> +static const struct coresight_ops dummy_source_cs_ops = {
>>> + .source_ops = &dummy_source_ops,
>>> +};
>>> +
>>> +static const struct coresight_ops_sink dummy_sink_ops = {
>>> + .enable = dummy_sink_enable,
>>> + .disable = dummy_sink_disable,
>>> +};
>>> +
>>> +static const struct coresight_ops dummy_sink_cs_ops = {
>>> + .sink_ops = &dummy_sink_ops,
>>> +};
>>> +
>>> +static int dummy_probe(struct platform_device *pdev)
>>> +{
>>> + struct device *dev = &pdev->dev;
>>> + struct device_node *node = dev->of_node;
>>> + struct coresight_platform_data *pdata;
>>> + struct dummy_drvdata *drvdata;
>>> + struct coresight_desc desc = { 0 };
>>> +
>>> + if (of_device_is_compatible(node, "arm,coresight-dummy-source")) {
>>> +
>>> + desc.name = coresight_alloc_device_name(&source_devs, dev);
>>> + if (!desc.name)
>>> + return -ENOMEM;
>>> +
>>> + desc.type = CORESIGHT_DEV_TYPE_SOURCE;
>>> + desc.subtype.source_subtype =
>>> + CORESIGHT_DEV_SUBTYPE_SOURCE_OTHERS;
>>> + desc.ops = &dummy_source_cs_ops;
>>> + } else if (of_device_is_compatible(node,
>>> "arm,coresight-dummy-sink")) {
>>> + desc.name = coresight_alloc_device_name(&sink_devs, dev);
>>> + if (!desc.name)
>>> + return -ENOMEM;
>>> +
>>> + desc.type = CORESIGHT_DEV_TYPE_SINK;
>>> + desc.subtype.sink_subtype = CORESIGHT_DEV_SUBTYPE_SINK_DUMMY;
>>> + desc.ops = &dummy_sink_cs_ops;
>>> + } else {
>>> + dev_err(dev, "Device type not set\n");
>>> + return -EINVAL;
>>> + }
>>> +
>>> + pdata = coresight_get_platform_data(dev);
>>> + if (IS_ERR(pdata))
>>> + return PTR_ERR(pdata);
>>> + pdev->dev.platform_data = pdata;
>>> +
>>> + drvdata = devm_kzalloc(dev, sizeof(*drvdata), GFP_KERNEL);
>>> + if (!drvdata)
>>> + return -ENOMEM; > +
>>> + drvdata->dev = &pdev->dev;
>>> + platform_set_drvdata(pdev, drvdata);
>>
>> As above, you may remove the drvdata entirely.
>>
> For some dummy sources, it's needed to allocate traceid for them in
> kernel driver, so this struct would be useful for that case.
>
> I will remove it now and upstream it in the further.
>
Hi Suzuki,
After checking, I find the drvdata struct is required for csdev which
would store the pointer of coresight_device, and it is also required for
traceid in the further. So I will keep drvdata in the next patch series.
Thanks,
Hao
> Thanks,
> Hao
>
>> Otherwise looks good to me
>>
>> Suzuki
>>
next prev parent reply other threads:[~2023-05-24 6:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 9:24 [PATCH v4 0/3] Add support to configure Coresight Dummy subunit Hao Zhang
2023-05-05 9:24 ` [PATCH v4 1/3] Coresight: Add coresight dummy driver Hao Zhang
2023-05-05 9:57 ` Suzuki K Poulose
2023-05-10 2:56 ` Hao Zhang
2023-05-24 6:12 ` Hao Zhang [this message]
2023-05-05 9:24 ` [PATCH v4 2/3] dt-bindings: arm: Add Coresight Dummy Trace Hao Zhang
2023-05-05 10:54 ` Suzuki K Poulose
2023-05-05 12:05 ` Leo Yan
2023-05-10 3:21 ` Hao Zhang
2023-05-07 8:04 ` Krzysztof Kozlowski
2023-05-15 5:52 ` Hao Zhang
2023-06-08 16:09 ` Rob Herring
2023-05-05 9:24 ` [PATCH v4 3/3] Documentation: trace: Add documentation for " Hao Zhang
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=0be9ea3f-d48c-c475-8081-b80cf2cd50dd@quicinc.com \
--to=quic_hazha@quicinc.com \
--cc=agross@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andersson@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=corbet@lwn.net \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konradybcio@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=quic_yuanfang@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=suzuki.poulose@arm.com \
/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).