[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87fszqfp6m.fsf@ashishki-desk.ger.corp.intel.com>
Date: Fri, 16 Apr 2021 14:23:45 +0300
From: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To: Tao Zhang <taozha@...eaurora.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>,
Suzuki K Poulose <suzuki.poulose@....com>
Cc: Tao Zhang <taozha@...eaurora.org>,
Mike Leach <mike.leach@...aro.org>,
Leo Yan <leo.yan@...aro.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
coresight@...ts.linaro.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Tingwei Zhang <tingwei@...eaurora.org>,
Mao Jinlong <jinlmao@...eaurora.org>,
Yuanfang Zhang <zhangyuanfang@...eaurora.org>,
alexander.shishkin@...ux.intel.com
Subject: Re: [PATCH v1 2/2] dt-bindings: arm: add property for coresight
component name
Tao Zhang <taozha@...eaurora.org> writes:
> Add property "coresight-name" for coresight component name. This
> allows coresight driver to read device name from device entries.
>
> Signed-off-by: Tao Zhang <taozha@...eaurora.org>
> ---
> Documentation/devicetree/bindings/arm/coresight.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/coresight.txt b/Documentation/devicetree/bindings/arm/coresight.txt
> index d711676..0e980ce 100644
> --- a/Documentation/devicetree/bindings/arm/coresight.txt
> +++ b/Documentation/devicetree/bindings/arm/coresight.txt
> @@ -103,6 +103,8 @@ its hardware characteristcs.
> powers down the coresight component also powers down and loses its
> context. This property is currently only used for the ETM 4.x driver.
>
> + * coresight-name: the name of the coresight devices.
Which devices? Also, is it a common practice to extend device tree
definitions based on arbitrary driver needs, or should there be some
sort of a discussion first?
Regards,
--
Alex
Powered by blists - more mailing lists