From: John Youn <John.Youn@synopsys.com>
To: Randy Li <ayaka@soulik.info>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: "John.Youn@synopsys.com" <John.Youn@synopsys.com>,
"kishon@ti.com" <kishon@ti.com>,
"felipe.balbi@linux.intel.com" <felipe.balbi@linux.intel.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"randy.li@rock-chips.com" <randy.li@rock-chips.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] phy: Add reset callback for not generic phy
Date: Tue, 25 Oct 2016 13:47:03 -0700 [thread overview]
Message-ID: <8c8d86e6-a3b1-a381-dd3f-70e43768cfb9@synopsys.com> (raw)
In-Reply-To: <1477404934-7425-1-git-send-email-ayaka@soulik.info>
On 10/25/2016 7:15 AM, Randy Li wrote:
> I forget to add a dummy function in case the CONFIG_GENERIC_PHY
> is disabled.
>
> Signed-off-by: Randy Li <ayaka@soulik.info>
Fixes: cac18ecb6f44 ("phy: Add reset callback")
Tested-by: John Youn <johnyoun@synopsys.com>
Hi Kishon,
Can you take this for 4.9-rc?
Thanks,
John
> ---
> include/linux/phy/phy.h | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
> index ee1bed7..78bb0d7 100644
> --- a/include/linux/phy/phy.h
> +++ b/include/linux/phy/phy.h
> @@ -253,6 +253,13 @@ static inline int phy_set_mode(struct phy *phy, enum phy_mode mode)
> return -ENOSYS;
> }
>
> +static inline int phy_reset(struct phy *phy)
> +{
> + if (!phy)
> + return 0;
> + return -ENOSYS;
> +}
> +
> static inline int phy_get_bus_width(struct phy *phy)
> {
> return -ENOSYS;
>
>
next prev parent reply other threads:[~2016-10-25 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 14:15 Randy Li
2016-10-25 20:47 ` John Youn [this message]
2016-10-26 20:14 ` Kishon Vijay Abraham I
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=8c8d86e6-a3b1-a381-dd3f-70e43768cfb9@synopsys.com \
--to=john.youn@synopsys.com \
--cc=ayaka@soulik.info \
--cc=felipe.balbi@linux.intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=randy.li@rock-chips.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
all inboxes | Powered by JetHome®