linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Chen <peter.chen@nxp.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: "vkoul@kernel.org" <vkoul@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Jun Li <jun.li@nxp.com>, dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH 1/1] phy: phy-cadence-salvo: add phy .init API
Date: Wed, 13 May 2020 10:51:15 +0000	[thread overview]
Message-ID: <20200513105141.GB3698@b29397-desktop> (raw)
In-Reply-To: <20200513025709.GB29070@a0393678ub>

On 20-05-13 08:27:09, Kishon Vijay Abraham I wrote:
> Hi Peter,
> 
> On Thu, May 07, 2020 at 01:21:20PM +0800, Peter Chen wrote:
> > .init is used for PHY's initialization, and .power_on/power_off are only
> > used for clock on and off.
> > 
> > Signed-off-by: Peter Chen <peter.chen@nxp.com>
> 
> This patch doesn't apply cleanly. Can you kindly check phy -next is
> proper since I expected this to merge cleanly?
> 

Hi Kishon,

I don't see my first salvo PHY at your phy -next tree

https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git/log/?h=next

But I do see it is on linux-next tree:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=50d35aa8c15f7210fe76de64b1940100b588bcae

What happened?

Peter
> Thanks
> Kishon
> > ---
> >  drivers/phy/cadence/phy-cadence-salvo.c | 12 +++++++++++-
> >  1 file changed, 11 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/phy/cadence/phy-cadence-salvo.c b/drivers/phy/cadence/phy-cadence-salvo.c
> > index fa666527356d..c2b6ddfe02e0 100644
> > --- a/drivers/phy/cadence/phy-cadence-salvo.c
> > +++ b/drivers/phy/cadence/phy-cadence-salvo.c
> > @@ -206,7 +206,7 @@ static struct cdns_reg_pairs cdns_nxp_sequence_pair[] = {
> >  };
> >  
> >  
> > -static int cdns_salvo_phy_power_on(struct phy *phy)
> > +static int cdns_salvo_phy_init(struct phy *phy)
> >  {
> >  	struct cdns_salvo_phy *salvo_phy = phy_get_drvdata(phy);
> >  	struct cdns_salvo_data *data = salvo_phy->data;
> > @@ -231,9 +231,18 @@ static int cdns_salvo_phy_power_on(struct phy *phy)
> >  
> >  	udelay(10);
> >  
> > +	clk_disable_unprepare(salvo_phy->clk);
> > +
> >  	return ret;
> >  }
> >  
> > +static int cdns_salvo_phy_power_on(struct phy *phy)
> > +{
> > +	struct cdns_salvo_phy *salvo_phy = phy_get_drvdata(phy);
> > +
> > +	return clk_prepare_enable(salvo_phy->clk);
> > +}
> > +
> >  static int cdns_salvo_phy_power_off(struct phy *phy)
> >  {
> >  	struct cdns_salvo_phy *salvo_phy = phy_get_drvdata(phy);
> > @@ -244,6 +253,7 @@ static int cdns_salvo_phy_power_off(struct phy *phy)
> >  }
> >  
> >  static struct phy_ops cdns_salvo_phy_ops = {
> > +	.init		= cdns_salvo_phy_init,
> >  	.power_on	= cdns_salvo_phy_power_on,
> >  	.power_off	= cdns_salvo_phy_power_off,
> >  	.owner		= THIS_MODULE,
> > -- 
> > 2.17.1
> > 

-- 

Thanks,
Peter Chen

  parent reply	other threads:[~2020-05-13 10:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-07  5:21 [PATCH 1/1] phy: phy-cadence-salvo: add phy .init API Peter Chen
     [not found] ` <20200513025709.GB29070@a0393678ub>
2020-05-13 10:51   ` Peter Chen [this message]
2020-05-13 11:00     ` Vinod Koul
2020-05-13 11:03     ` 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=20200513105141.GB3698@b29397-desktop \
    --to=peter.chen@nxp.com \
    --cc=jun.li@nxp.com \
    --cc=kishon@ti.com \
    --cc=linux-imx@nxp.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=vkoul@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).