From: Stephen Boyd <sboyd@kernel.org>
To: Andrew Davis <afd@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Andrew Davis <afd@ti.com>
Subject: Re: [PATCH 2/2] dt-bindings: clock: ehrpwm: Remove unneeded syscon compatible
Date: Fri, 16 Jun 2023 11:58:24 -0700 [thread overview]
Message-ID: <0ea8308998c8ceffd1b0564d25579077.sboyd@kernel.org> (raw)
In-Reply-To: <20230516184626.154892-2-afd@ti.com>
Quoting Andrew Davis (2023-05-16 11:46:26)
> This node's register space is not accessed by any other node, which
> is the traditional use for the "syscon" hint. It looks to have been
> added here to make use of a Linux kernel helper syscon_node_to_regmap().
> The Linux driver now uses a more appropriate helper that does not
> require the hint, so let's remove it from the binding.
>
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
Applied to clk-next
next prev parent reply other threads:[~2023-06-16 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 18:46 [PATCH 1/2] clk: keystone: syscon-clk: Allow the clock node to not be of type syscon Andrew Davis
2023-05-16 18:46 ` [PATCH 2/2] dt-bindings: clock: ehrpwm: Remove unneeded syscon compatible Andrew Davis
2023-05-17 4:36 ` Vignesh Raghavendra
2023-05-17 17:14 ` Andrew Davis
2023-05-17 7:53 ` Krzysztof Kozlowski
2023-06-23 19:59 ` Rob Herring
2023-06-23 20:18 ` Andrew Davis
2023-05-17 8:30 ` Krzysztof Kozlowski
2023-06-16 18:58 ` Stephen Boyd [this message]
2023-06-16 18:58 ` [PATCH 1/2] clk: keystone: syscon-clk: Allow the clock node to not be of type syscon Stephen Boyd
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=0ea8308998c8ceffd1b0564d25579077.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).