public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: "Heiko Stübner" <heiko@sntech.de>,
	"Shawn Lin" <shawn.lin@rock-chips.com>
Cc: <linux-kernel@vger.kernel.org>,
	<linux-rockchip@lists.infradead.org>,
	Doug Anderson <dianders@chromium.org>,
	Brian Norris <briannorris@chromium.org>,
	Wenrui Li <wenrui.li@rock-chips.com>,
	Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 2/2] phy: add a driver for the Rockchip SoC internal PCIe PHY
Date: Thu, 1 Sep 2016 10:35:16 +0530	[thread overview]
Message-ID: <57C7B70C.3020101@ti.com> (raw)
In-Reply-To: <6005500.MI6i4QbaFN@diego>



On Wednesday 31 August 2016 07:38 PM, Heiko Stübner wrote:
> Hi,
> 
> Am Samstag, 20. August 2016, 10:53:37 schrieb Shawn Lin:
>> This patch to add a generic PHY driver for rockchip PCIe PHY.
>> Access the PHY via registers provided by GRF (general register
>> files) module.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
> 
> seems I'm late to the party, but when looking if I can apply the pcie-
> devicetree patches, I found that the phy is still pending.
> 
> Apart from some error-message nitpicks below, this looks ok to me. I don't 
> know enough about the actual pci phy part though.
> 
> Kishon, is this on your radar?

yes.. can the nipicks be fixed and posted asap?

Thanks
Kishon

> 
> [...]
> 
>> +static int rockchip_pcie_phy_power_off(struct phy *phy)
>> +{
>> +	struct rockchip_pcie_phy *rk_phy = phy_get_drvdata(phy);
>> +	int err = 0;
>> +
>> +	err = reset_control_assert(rk_phy->phy_rst);
>> +	if (err) {
>> +		pr_err("assert phy_rst err %d\n", err);
> 
> 	dev_err(phy->dev, ...)
> 
> probably the same for all other pr_err invocations
> 
> 
>> +		return err;
>> +	}
>> +
>> +	return 0;
>> +}
> 
> [...]
> 
>> +static const struct of_device_id rockchip_pcie_phy_dt_ids[] = {
>> +	{
>> +		.compatible = "rockchip,rk3399-pcie-phy",
>> +		.data = &rk3399_pcie_data,
>> +	},
>> +	{}
>> +};
>> +
>> +MODULE_DEVICE_TABLE(of, rockchip_pcie_phy_dt_ids);
>> +
>> +static int rockchip_pcie_phy_probe(struct platform_device *pdev)
>> +{
>> +	struct device *dev = &pdev->dev;
>> +	struct rockchip_pcie_phy *rk_phy;
>> +	struct phy *generic_phy;
>> +	struct phy_provider *phy_provider;
>> +	struct regmap *grf;
>> +	const struct of_device_id *of_id;
>> +
>> +	grf = syscon_node_to_regmap(dev->parent->of_node);
>> +	if (IS_ERR(grf)) {
>> +		dev_err(dev, "Missing rockchip,grf property\n");
> 
> 		dev_err(dev, "Cannot find GRF syscon\n");
> 
> 
> Heiko
> 

      reply	other threads:[~2016-09-01  5:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20  2:53 [PATCH v5 1/2] Documentation: bindings: add dt documentation for Rockchip PCIe PHY Shawn Lin
2016-08-20  2:53 ` [PATCH v5 2/2] phy: add a driver for the Rockchip SoC internal " Shawn Lin
2016-08-31 14:08   ` Heiko Stübner
2016-09-01  5:05     ` Kishon Vijay Abraham I [this message]

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=57C7B70C.3020101@ti.com \
    --to=kishon@ti.com \
    --cc=briannorris@chromium.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=heiko@sntech.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=wenrui.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