From: Kishon Vijay Abraham I <kishon@a0393678ub>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Randy Li <ayaka@soulik.info>,
linux-usb@vger.kernel.org, John.Youn@synopsys.com, kishon@ti.com,
felipe.balbi@linux.intel.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, randy.li@rock-chips.com
Subject: Re: [RESEND PATCH v7 1/4] phy: Add reset callback
Date: Sat, 10 Sep 2016 17:27:47 +0530 [thread overview]
Message-ID: <20160910115747.GA10077@a0393678ub> (raw)
In-Reply-To: <8774766.IvFq1IoyNk@phil>
Hi,
On Sat, Sep 10, 2016 at 10:51:00AM +0200, Heiko Stuebner wrote:
> Hi Randy,
>
> Am Samstag, 10. September 2016, 02:59:37 CEST schrieb Randy Li:
> > The only use for this is for solving a hardware design problem in
> > usb of Rockchip RK3288.
> >
> > Signed-off-by: Randy Li <ayaka@soulik.info>
>
> When sending new versions, please carry over received Reviewed- / Tested- /
> Acked-by tags received on old versions.
>
> So again, to me this looks good.
>
> Although Kishon suggested earlier to have the init callback do the reset and
> simply call it again in the reset-case, the whole refcounting done in phy_init
> and phy_exit (phy->init_count) really shows that init and exit should be
> called pairwise, so that extra reset callback seems justified, so from my phy-
> noob-pov
yeah, that makes sense. Moreover I see few more users wanting to use reset.
Btw fixed a couple of checkpatch warning before merging this
WARNING: Missing a blank line after declarations
#82: FILE: drivers/phy/phy-core.c:363:
+ int ret;
+ if (!phy || !phy->ops->reset)
WARNING: 'reseting' may be misspelled - perhaps 'resetting'?
#104: FILE: include/linux/phy/phy.h:39:
+ * @reset: reseting the phy
-Kishon
>
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>
> > ---
> > drivers/phy/phy-core.c | 14 ++++++++++++++
> > include/linux/phy/phy.h | 3 +++
> > 2 files changed, 17 insertions(+)
> >
> > diff --git a/drivers/phy/phy-core.c b/drivers/phy/phy-core.c
> > index 8eca906..32e838d 100644
> > --- a/drivers/phy/phy-core.c
> > +++ b/drivers/phy/phy-core.c
> > @@ -357,6 +357,20 @@ int phy_set_mode(struct phy *phy, enum phy_mode mode)
> > }
> > EXPORT_SYMBOL_GPL(phy_set_mode);
> >
> > +int phy_reset(struct phy *phy)
> > +{
> > + int ret;
> > + if (!phy || !phy->ops->reset)
> > + return 0;
> > +
> > + mutex_lock(&phy->mutex);
> > + ret = phy->ops->reset(phy);
> > + mutex_unlock(&phy->mutex);
> > +
> > + return ret;
> > +}
> > +EXPORT_SYMBOL_GPL(phy_reset);
> > +
> > /**
> > * _of_phy_get() - lookup and obtain a reference to a phy by phandle
> > * @np: device_node for which to get the phy
> > diff --git a/include/linux/phy/phy.h b/include/linux/phy/phy.h
> > index f08b672..7978df6 100644
> > --- a/include/linux/phy/phy.h
> > +++ b/include/linux/phy/phy.h
> > @@ -36,6 +36,7 @@ enum phy_mode {
> > * @power_on: powering on the phy
> > * @power_off: powering off the phy
> > * @set_mode: set the mode of the phy
> > + * @reset: reseting the phy
> > * @owner: the module owner containing the ops
> > */
> > struct phy_ops {
> > @@ -44,6 +45,7 @@ struct phy_ops {
> > int (*power_on)(struct phy *phy);
> > int (*power_off)(struct phy *phy);
> > int (*set_mode)(struct phy *phy, enum phy_mode mode);
> > + int (*reset)(struct phy *phy);
> > struct module *owner;
> > };
> >
> > @@ -136,6 +138,7 @@ int phy_exit(struct phy *phy);
> > int phy_power_on(struct phy *phy);
> > int phy_power_off(struct phy *phy);
> > int phy_set_mode(struct phy *phy, enum phy_mode mode);
> > +int phy_reset(struct phy *phy);
> > static inline int phy_get_bus_width(struct phy *phy)
> > {
> > return phy->attrs.bus_width;
>
>
next prev parent reply other threads:[~2016-09-10 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 18:59 [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform Randy Li
2016-09-09 18:59 ` [RESEND PATCH v7 2/4] phy: rockchip-usb: use rockchip_usb_phy_reset to reset phy during wakeup Randy Li
2016-09-19 21:28 ` Rob Herring
[not found] ` <1473447580-10369-1-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-09 18:59 ` [RESEND PATCH v7 1/4] phy: Add reset callback Randy Li
[not found] ` <1473447580-10369-2-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-10 8:51 ` Heiko Stuebner
2016-09-10 11:57 ` Kishon Vijay Abraham I [this message]
2016-09-09 18:59 ` [RESEND PATCH v7 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform Randy Li
[not found] ` <1473447580-10369-4-git-send-email-ayaka-xPW3/0Ywev/iB9QmIjCX8w@public.gmane.org>
2016-09-09 19:40 ` Sergei Shtylyov
2016-09-11 10:03 ` kbuild test robot
2016-09-09 18:59 ` [RESEND PATCH v7 4/4] ARM: dts: rockchip: Point rk3288 dwc2 usb at the full PHY reset Randy Li
2016-09-13 11:06 ` [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform Heiko Stuebner
2016-09-13 11:26 ` ayaka
2016-09-13 14:30 ` Heiko Stuebner
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=20160910115747.GA10077@a0393678ub \
--to=kishon@a0393678ub \
--cc=John.Youn@synopsys.com \
--cc=ayaka@soulik.info \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).