All of lore.kernel.org
 help / color / mirror / Atom feed
From: lyz@rock-chips.com (Yunzhi Li)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY
Date: Fri, 12 Dec 2014 11:43:25 +0800	[thread overview]
Message-ID: <548A645D.8010608@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=WcAJAgj2triu1W4863BT1ew2wf-z6YNHHwiDKpnYmK4w@mail.gmail.com>

Hi Doug:

On 2014/12/12 2:09, Doug Anderson wrote:
> Yunzhi,
>
> On Thu, Dec 11, 2014 at 1:55 AM, Yunzhi Li <lyz@rock-chips.com> wrote:
>> +               rk_phy->clk = of_clk_get(child, 0);
>> +               if (IS_ERR(rk_phy->clk)) {
>> +                       dev_warn(dev, "failed to get clock\n");
>> +                       rk_phy->clk = NULL;
>> +               }
> The device tree bindings don't specify a clock and the "dtsi" added to
> rk3288 don't reference a clock.  Take that code out and avoid a
> warning in the logs at bootup.
>
> ...or should there be a clock?
Actually, there is a clk gating control bit in CRU for each usb phy and I
think we should manage these clocks by the usb phy driver, so I will add
clock property to usb PHYs nodes in next version of patche set.

>
>> +               rk_phy->phy = devm_phy_create(dev, NULL, &ops);
> This has the wrong number of arguments.  Even before the change that
> added the 4th argument, this is still wrong because "ops" is supposed
> to be the 2nd argument, not the 3rd.
>
> ...so I'm confused how this compiled for you.  I think this ought to be:
>
> rk_phy->phy = devm_phy_create(dev, child, &ops, NULL);
>
> ...but please correct me if I'm mistaken!
>
>
>

WARNING: multiple messages have this Message-ID (diff)
From: Yunzhi Li <lyz@rock-chips.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Tao Huang" <huangtao@rock-chips.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	Chris <zyw@rock-chips.com>, "Eddie Cai" <cf@rock-chips.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Olof Johansson" <olof@lixom.net>,
	jwerner@chromium.org,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Grant Likely" <grant.likely@linaro.org>
Subject: Re: [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY
Date: Fri, 12 Dec 2014 11:43:25 +0800	[thread overview]
Message-ID: <548A645D.8010608@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=WcAJAgj2triu1W4863BT1ew2wf-z6YNHHwiDKpnYmK4w@mail.gmail.com>

Hi Doug:

On 2014/12/12 2:09, Doug Anderson wrote:
> Yunzhi,
>
> On Thu, Dec 11, 2014 at 1:55 AM, Yunzhi Li <lyz@rock-chips.com> wrote:
>> +               rk_phy->clk = of_clk_get(child, 0);
>> +               if (IS_ERR(rk_phy->clk)) {
>> +                       dev_warn(dev, "failed to get clock\n");
>> +                       rk_phy->clk = NULL;
>> +               }
> The device tree bindings don't specify a clock and the "dtsi" added to
> rk3288 don't reference a clock.  Take that code out and avoid a
> warning in the logs at bootup.
>
> ...or should there be a clock?
Actually, there is a clk gating control bit in CRU for each usb phy and I
think we should manage these clocks by the usb phy driver, so I will add
clock property to usb PHYs nodes in next version of patche set.

>
>> +               rk_phy->phy = devm_phy_create(dev, NULL, &ops);
> This has the wrong number of arguments.  Even before the change that
> added the 4th argument, this is still wrong because "ops" is supposed
> to be the 2nd argument, not the 3rd.
>
> ...so I'm confused how this compiled for you.  I think this ought to be:
>
> rk_phy->phy = devm_phy_create(dev, child, &ops, NULL);
>
> ...but please correct me if I'm mistaken!
>
>
>

WARNING: multiple messages have this Message-ID (diff)
From: Yunzhi Li <lyz@rock-chips.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "Heiko Stübner" <heiko@sntech.de>,
	jwerner@chromium.org, "Olof Johansson" <olof@lixom.net>,
	"Tao Huang" <huangtao@rock-chips.com>, Chris <zyw@rock-chips.com>,
	"Eddie Cai" <cf@rock-chips.com>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"Grant Likely" <grant.likely@linaro.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY
Date: Fri, 12 Dec 2014 11:43:25 +0800	[thread overview]
Message-ID: <548A645D.8010608@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=WcAJAgj2triu1W4863BT1ew2wf-z6YNHHwiDKpnYmK4w@mail.gmail.com>

Hi Doug:

On 2014/12/12 2:09, Doug Anderson wrote:
> Yunzhi,
>
> On Thu, Dec 11, 2014 at 1:55 AM, Yunzhi Li <lyz@rock-chips.com> wrote:
>> +               rk_phy->clk = of_clk_get(child, 0);
>> +               if (IS_ERR(rk_phy->clk)) {
>> +                       dev_warn(dev, "failed to get clock\n");
>> +                       rk_phy->clk = NULL;
>> +               }
> The device tree bindings don't specify a clock and the "dtsi" added to
> rk3288 don't reference a clock.  Take that code out and avoid a
> warning in the logs at bootup.
>
> ...or should there be a clock?
Actually, there is a clk gating control bit in CRU for each usb phy and I
think we should manage these clocks by the usb phy driver, so I will add
clock property to usb PHYs nodes in next version of patche set.

>
>> +               rk_phy->phy = devm_phy_create(dev, NULL, &ops);
> This has the wrong number of arguments.  Even before the change that
> added the 4th argument, this is still wrong because "ops" is supposed
> to be the 2nd argument, not the 3rd.
>
> ...so I'm confused how this compiled for you.  I think this ought to be:
>
> rk_phy->phy = devm_phy_create(dev, child, &ops, NULL);
>
> ...but please correct me if I'm mistaken!
>
>
>



  parent reply	other threads:[~2014-12-12  3:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  9:55 [PATCH v6 0/5] Patches to add support for Rockchip usb PHYs Yunzhi Li
2014-12-11  9:55 ` Yunzhi Li
2014-12-11  9:55 ` Yunzhi Li
2014-12-11  9:55 ` [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal USB2.0 PHY Yunzhi Li
2014-12-11  9:55   ` Yunzhi Li
2014-12-11 10:27   ` Kishon Vijay Abraham I
2014-12-11 10:27     ` Kishon Vijay Abraham I
2014-12-11 10:27     ` Kishon Vijay Abraham I
2014-12-11 13:45     ` Yunzhi Li
2014-12-11 13:45       ` Yunzhi Li
2014-12-11 13:45       ` Yunzhi Li
2014-12-12  5:34       ` Kishon Vijay Abraham I
2014-12-12  5:34         ` Kishon Vijay Abraham I
2014-12-12  5:34         ` Kishon Vijay Abraham I
2014-12-11 18:41     ` Doug Anderson
2014-12-11 18:41       ` Doug Anderson
2014-12-12  5:47       ` Kishon Vijay Abraham I
2014-12-12  5:47         ` Kishon Vijay Abraham I
2014-12-12  5:47         ` Kishon Vijay Abraham I
2014-12-12  5:51         ` Doug Anderson
2014-12-11 18:09   ` Doug Anderson
2014-12-11 18:09     ` Doug Anderson
2014-12-12  3:05     ` Doug Anderson
2014-12-12  3:05       ` Doug Anderson
2014-12-12  3:05       ` Doug Anderson
2014-12-12  3:43     ` Yunzhi Li [this message]
2014-12-12  3:43       ` Yunzhi Li
2014-12-12  3:43       ` Yunzhi Li
2014-12-11  9:55 ` [PATCH v6 2/5] Documentation: bindings: add dt documentation for Rockchip usb PHY Yunzhi Li
     [not found]   ` <1418291722-25448-3-git-send-email-lyz-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-12-11 18:46     ` Doug Anderson
2014-12-11 18:46       ` Doug Anderson
2014-12-11 18:49       ` Doug Anderson
2014-12-11  9:55 ` [PATCH v6 3/5] usb: dwc2: add generic PHY framework support for dwc2 usb controler platform driver Yunzhi Li
2014-12-11  9:55 ` [PATCH v6 4/5] ARM: dts: rockchip: add rk3288 usb PHY Yunzhi Li
2014-12-11  9:55   ` Yunzhi Li
2014-12-11 10:11 ` [PATCH v6 5/5] ARM: dts: rockchip: Enable usb PHY on rk3288-evb board Yunzhi Li
2014-12-11 10:11   ` Yunzhi Li

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=548A645D.8010608@rock-chips.com \
    --to=lyz@rock-chips.com \
    --cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.