linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [V5 PATCH 25/26] usb: otg: mv_otg: add device tree support
Date: Thu, 24 Jan 2013 11:02:37 +0000	[thread overview]
Message-ID: <20130124110237.GL32237@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1359009530-28182-26-git-send-email-chao.xie@marvell.com>

On Thu, Jan 24, 2013 at 06:38:49AM +0000, Chao Xie wrote:
> All blocks are removed. Add the device tree support for otg.

As with mv_udc, this binding should be documented. Please Cc
devicetree-discuss when you have one.

> 
> Signed-off-by: Chao Xie <chao.xie@marvell.com>
> ---
>  drivers/usb/otg/mv_otg.c |  128 +++++++++++++++++++++++++++++++++++++--------
>  drivers/usb/otg/mv_otg.h |    6 +-
>  2 files changed, 108 insertions(+), 26 deletions(-)
> 
> diff --git a/drivers/usb/otg/mv_otg.c b/drivers/usb/otg/mv_otg.c
> index 379df92..3aa7fdc 100644
> --- a/drivers/usb/otg/mv_otg.c
> +++ b/drivers/usb/otg/mv_otg.c
> @@ -17,6 +17,7 @@
>  #include <linux/device.h>
>  #include <linux/proc_fs.h>
>  #include <linux/clk.h>
> +#include <linux/of.h>
>  #include <linux/workqueue.h>
>  #include <linux/platform_device.h>
>  
> @@ -333,7 +334,7 @@ static void mv_otg_update_inputs(struct mv_otg *mvotg)
>  	else
>  		otg_ctrl->id = !!(otgsc & OTGSC_STS_USB_ID);
>  
> -	if (mvotg->pdata->otg_force_a_bus_req && !otg_ctrl->id)
> +	if (mvotg->otg_force_a_bus_req && !otg_ctrl->id)
>  		otg_ctrl->a_bus_req = 1;
>  
>  	otg_ctrl->a_sess_vld = !!(otgsc & OTGSC_STS_A_SESSION_VALID);
> @@ -690,21 +691,69 @@ int mv_otg_remove(struct platform_device *pdev)
>  	return 0;
>  }
>  
> +static int mv_otg_parse_dt(struct platform_device *pdev,
> +				struct mv_otg *mvotg)
> +{
> +	struct device_node *np = pdev->dev.of_node;
> +	unsigned int clks_num;
> +	unsigned int val;
> +	int i, ret;
> +	const char *clk_name;
> +
> +	if (!np)
> +		return 1;
> +
> +	clks_num = of_property_count_strings(np, "clocks");
> +	if (clks_num < 0)
> +		return clks_num;
> +
> +	mvotg->clk = devm_kzalloc(&pdev->dev,
> +		sizeof(struct clk *) * clks_num, GFP_KERNEL);
> +	if (mvotg->clk == NULL)
> +		return -ENOMEM;
> +
> +	for (i = 0; i < clks_num; i++) {
> +		ret = of_property_read_string_index(np, "clocks", i,
> +			&clk_name);
> +		if (ret)
> +			return ret;
> +		mvotg->clk[i] = devm_clk_get(&pdev->dev, clk_name);
> +		if (IS_ERR(mvotg->clk[i]))
> +			return PTR_ERR(mvotg->clk[i]);
> +	}

Again, it seems a shame there's no devm_of_clk_get.

> +
> +	mvotg->clknum = clks_num;
> +
> +	ret = of_property_read_u32(np, "extern_attr", &mvotg->extern_attr);
> +	if (ret)
> +		return ret;
> +
> +	ret = of_property_read_u32(np, "mode", &mvotg->mode);
> +	if (ret)
> +		return ret;

I *really* don't like this, for the same reasons I stated in reply to the
mv_udc patch.

> +
> +	ret = of_property_read_u32(np, "force_a_bus_req", &val);
> +	if (ret)
> +		return ret;
> +	mvotg->otg_force_a_bus_req = !!val;

In devicetree, the typical way to handle a boolean case like this would be to
have a valueless property. If present, the property is true, if not present
it's considered to default to false:

device at 4000 {
	compatible = "manufacturer,some-device";
	reg = <0x4000, 0x1000>;
	manufacturer,boolean-property; /* no value, true if present */
};

Properties which may only have a meaning on one manufacturer's devices are also
typically prefixed with the manufacturer similarly to compatible strings, e.g.
"mrvl,force-a-bus-req".

There may also be a better name for this property.

> +
> +	ret = of_property_read_u32(np, "disable_clock_gating", &val);
> +	if (ret)
> +		return ret;
> +	mvotg->clock_gating = !val;

You can do the same here, but with the logic inverted.

> +
> +	return 0;
> +}
> +
>  static int mv_otg_probe(struct platform_device *pdev)
>  {
> -	struct mv_usb_platform_data *pdata = pdev->dev.platform_data;
>  	struct mv_otg *mvotg;
>  	struct usb_otg *otg;
>  	struct resource *r;
> -	int retval = 0, clk_i, i;
> +	int retval = 0, i;
>  	size_t size;
>  
> -	if (pdata == NULL) {
> -		dev_err(&pdev->dev, "failed to get platform data\n");
> -		return -ENODEV;
> -	}
> -
> -	size = sizeof(*mvotg) + sizeof(struct clk *) * pdata->clknum;
> +	size = sizeof(*mvotg);
>  	mvotg = devm_kzalloc(&pdev->dev, size, GFP_KERNEL);
>  	if (!mvotg) {
>  		dev_err(&pdev->dev, "failed to allocate memory!\n");
> @@ -718,17 +767,45 @@ static int mv_otg_probe(struct platform_device *pdev)
>  	platform_set_drvdata(pdev, mvotg);
>  
>  	mvotg->pdev = pdev;
> -	mvotg->extern_attr = pdata->extern_attr;
> -	mvotg->pdata = pdata;
>  
> -	mvotg->clknum = pdata->clknum;
> -	for (clk_i = 0; clk_i < mvotg->clknum; clk_i++) {
> -		mvotg->clk[clk_i] = devm_clk_get(&pdev->dev,
> +	retval = mv_otg_parse_dt(pdev, mvotg);
> +	if (retval > 0) {
> +		struct mv_usb_platform_data *pdata = pdev->dev.platform_data;
> +		/* no CONFIG_OF */
> +		int clk_i = 0;
> +
> +		if (pdata == NULL) {
> +			dev_err(&pdev->dev, "missing platform_data\n");
> +			return -ENODEV;
> +		}
> +		mvotg->extern_attr = pdata->extern_attr;
> +		mvotg->mode = pdata->mode;
> +		mvotg->clknum = pdata->clknum;
> +		mvotg->otg_force_a_bus_req = pdata->otg_force_a_bus_req;
> +		if (pdata->disable_otg_clock_gating)
> +			mvotg->clock_gating = 0;
> +
> +		size = sizeof(struct clk *) * mvotg->clknum;
> +		mvotg->clk = devm_kzalloc(&pdev->dev, size, GFP_KERNEL);
> +		if (mvotg->clk == NULL) {
> +			dev_err(&pdev->dev,
> +				"failed to allocate memory for clk\n");
> +			return -ENOMEM;
> +		}
> +
> +		for (clk_i = 0; clk_i < mvotg->clknum; clk_i++) {
> +			mvotg->clk[clk_i] = devm_clk_get(&pdev->dev,
>  						pdata->clkname[clk_i]);
> -		if (IS_ERR(mvotg->clk[clk_i])) {
> -			retval = PTR_ERR(mvotg->clk[clk_i]);
> -			return retval;
> +			if (IS_ERR(mvotg->clk[clk_i])) {
> +				dev_err(&pdev->dev, "failed to get clk %s\n",
> +					pdata->clkname[clk_i]);
> +				retval = PTR_ERR(mvotg->clk[clk_i]);
> +				return retval;

You don't need to go via retval here.

[...]

Thanks,
Mark.

  reply	other threads:[~2013-01-24 11:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  6:38 [V5 PATCH 00/26] mv-usb fix and enhancement patches Chao Xie
2013-01-24  6:38 ` [V5 PATCH 01/26] usb: gadget: mv_udc: use udc_start and udc_stop functions Chao Xie
2013-01-24  6:38 ` [V5 PATCH 02/26] usb: gadget: mv_udc: use devm_xxx for probe Chao Xie
2013-01-24  6:38 ` [V5 PATCH 03/26] usb: gadget: mv_udc: fix the warning of mv_udc_remove Chao Xie
2013-01-24  6:38 ` [V5 PATCH 04/26] usb: otg: mv_otg: use devm_xxx for probe Chao Xie
2013-01-24  6:38 ` [V5 PATCH 05/26] usb: host: ehci-mv: remove unused variable Chao Xie
2013-01-24  6:38 ` [V5 PATCH 06/26] usb: gadget: mv_udc: fix the value of tranceiver Chao Xie
2013-01-24  6:38 ` [V5 PATCH 07/26] usb: gadget: mv_udc: make mv_udc depends on ARCH_MMP or ARCH_PXA Chao Xie
2013-01-24  9:08   ` Felipe Balbi
2013-01-25  1:57     ` chao xie
2013-01-24  6:38 ` [V5 PATCH 08/26] usb: phy: mv_usb2: add PHY driver for marvell usb2 controller Chao Xie
2013-01-24  6:38 ` [V5 PATCH 09/26] usb: gadget: mv_udc: use PHY driver for udc Chao Xie
2013-01-24  6:38 ` [V5 PATCH 10/26] usb: ehci: ehci-mv: use PHY driver for ehci Chao Xie
2013-01-24  6:38 ` [V5 PATCH 11/26] usb: otg: mv_otg: use PHY driver for otg Chao Xie
2013-01-24  6:38 ` [V5 PATCH 12/26] arm: mmp2: change the defintion of usb devices Chao Xie
2013-01-24  6:38 ` [V5 PATCH 13/26] arm: pxa910: " Chao Xie
2013-01-24  6:38 ` [V5 PATCH 14/26] arm: brownstone: add usb support for the board Chao Xie
2013-01-24  6:38 ` [V5 PATCH 15/26] arm: ttc_dkb: add usb support Chao Xie
2013-01-24  6:38 ` [V5 PATCH 16/26] arm: mmp: remove the usb phy setting Chao Xie
2013-01-24  6:38 ` [V5 PATCH 17/26] arm: mmp: remove usb devices from pxa168 Chao Xie
2013-01-24  6:38 ` [V5 PATCH 18/26] usb: phy: mv_usb2_phy: add externel chip support Chao Xie
2013-01-24  6:38 ` [V5 PATCH 19/26] usb: gadget: mv_udc: add extern " Chao Xie
2013-01-24  6:38 ` [V5 PATCH 20/26] usb: ehci: ehci-mv: " Chao Xie
2013-01-24  6:38 ` [V5 PATCH 21/26] usb: otg: mv_otg: " Chao Xie
2013-01-24  6:38 ` [V5 PATCH 22/26] arm: mmp: add extern chip support for brownstone Chao Xie
2013-01-24  6:38 ` [V5 PATCH 23/26] arm: mmp: add extern chip support for ttc_dkb Chao Xie
2013-01-24  6:38 ` [V5 PATCH 24/26] usb: gadget: mv_udc: add device tree support Chao Xie
2013-01-24 10:49   ` Mark Rutland
2013-01-25  2:13     ` chao xie
2013-01-25  9:51       ` Mark Rutland
2013-01-24  6:38 ` [V5 PATCH 25/26] usb: otg: mv_otg: " Chao Xie
2013-01-24 11:02   ` Mark Rutland [this message]
2013-01-25  2:16     ` chao xie
2013-01-24  6:38 ` [V5 PATCH 26/26] usb: ehci: ehci-mv: " Chao Xie
2013-01-24 11:16   ` Mark Rutland
2013-01-25  2:27     ` chao xie
2013-01-25  9:55       ` Mark Rutland

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=20130124110237.GL32237@e106331-lin.cambridge.arm.com \
    --to=mark.rutland@arm.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 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).