Messages in this thread | | | Date | Thu, 16 Mar 2023 10:55:27 +0000 | Subject | Re: [PATCH v1 0/3] Add support to configure Coresight Dummy subunit | From | Suzuki K Poulose <> |
| |
On 16/03/2023 03:20, Hao Zhang wrote: > Introduction of Coresight Dummy subunit > The Coresight Dummy subunit is for Coresight Dummy component, there are some > specific Coresight devices that HLOS don't have permission to access. Such as
What is HLOS ?
> some TPDMs, they would be configured in NON-HLOS side, but it's necessary to
What is NON-HLOS ?
> build Coresight path for it to debug. So there need driver to register dummy > devices as Coresight devices.
Build a path for who to debug ? If this is used by some privileged software, shouldn't that do all of the work ?
Suzuki
> > Commit link: > https://git.codelinaro.org/clo/linux-kernel/coresight/-/tree/coresight-dummy > > Hao Zhang (3): > Coresight: Add coresight dummy driver > dt-bindings: arm: Add Coresight Dummy Trace YAML schema > Documentation: trace: Add documentation for Coresight Dummy Trace > > .../bindings/arm/qcom,coresight-dummy.yaml | 129 +++++++++++++ > .../trace/coresight/coresight-dummy.rst | 58 ++++++ > drivers/hwtracing/coresight/Kconfig | 11 ++ > drivers/hwtracing/coresight/Makefile | 1 + > drivers/hwtracing/coresight/coresight-dummy.c | 176 ++++++++++++++++++ > 5 files changed, 375 insertions(+) > create mode 100644 Documentation/devicetree/bindings/arm/qcom,coresight-dummy.yaml > create mode 100644 Documentation/trace/coresight/coresight-dummy.rst > create mode 100644 drivers/hwtracing/coresight/coresight-dummy.c >
| |