From: Kishon Vijay Abraham I <kishon@ti.com>
To: Anil Joy Varughese <aniljoy@cadence.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Cc: <mparab@cadence.com>, <rafalc@cadence.com>
Subject: Re: [PATCH] bindings:phy Mark phy_clk binding as deprecated in Cadence Sierra Phy.
Date: Mon, 18 Nov 2019 13:32:13 +0530 [thread overview]
Message-ID: <dce65150-cbd8-eb4d-5778-47658a719eb5@ti.com> (raw)
In-Reply-To: <1574062988-4751-1-git-send-email-aniljoy@cadence.com>
Anil,
On 18/11/19 1:13 PM, Anil Joy Varughese wrote:
> Updated the Sierra Phy binding doc to mark phy_clk as deprecated.
This should also indicate why your are deprecating it.
Thanks
Kishon
>
> Signed-off-by: Anil Joy Varughese <aniljoy@cadence.com>
> ---
> .../devicetree/bindings/phy/phy-cadence-sierra.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt b/Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt
> index 6e1b47b..9a42b46 100644
> --- a/Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt
> +++ b/Documentation/devicetree/bindings/phy/phy-cadence-sierra.txt
> @@ -5,7 +5,7 @@ Required properties:
> - compatible: cdns,sierra-phy-t0
> - clocks: Must contain an entry in clock-names.
> See ../clocks/clock-bindings.txt for details.
> -- clock-names: Must be "phy_clk"
> +- clock-names: Must be "phy_clk". This is deprecated and should not be used with newer bindings.
> - resets: Must contain an entry for each in reset-names.
> See ../reset/reset.txt for details.
> - reset-names: Must include "sierra_reset" and "sierra_apb".
>
next prev parent reply other threads:[~2019-11-18 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 7:43 Anil Joy Varughese
2019-11-18 8:02 ` Kishon Vijay Abraham I [this message]
2019-11-18 9:00 ` Anil Joy Varughese
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=dce65150-cbd8-eb4d-5778-47658a719eb5@ti.com \
--to=kishon@ti.com \
--cc=aniljoy@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mparab@cadence.com \
--cc=rafalc@cadence.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®