[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD=FV=WcAJAgj2triu1W4863BT1ew2wf-z6YNHHwiDKpnYmK4w@mail.gmail.com>
Date: Thu, 11 Dec 2014 10:09:40 -0800
From: Doug Anderson <dianders@...omium.org>
To: Yunzhi Li <lyz@...k-chips.com>
Cc: Heiko Stübner <heiko@...ech.de>,
jwerner@...omium.org, Olof Johansson <olof@...om.net>,
Tao Huang <huangtao@...k-chips.com>,
Chris <zyw@...k-chips.com>, Eddie Cai <cf@...k-chips.com>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Kishon Vijay Abraham I <kishon@...com>,
Grant Likely <grant.likely@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v6 1/5] phy: add a driver for the Rockchip SoC internal
USB2.0 PHY
Yunzhi,
On Thu, Dec 11, 2014 at 1:55 AM, Yunzhi Li <lyz@...k-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?
> + 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!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists