From: Felipe Balbi <balbi@ti.com>
To: George Cherian <george.cherian@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
tony@atomide.com, balbi@ti.com, kishon@ti.com, rob@landley.net,
ijc+devicetree@hellion.org.uk, swarren@wwwdotorg.org,
mark.rutland@arm.com, pawel.moll@arm.com,
rob.herring@calxeda.com, gregkh@linuxfoundation.org
Subject: Re: [PATCH v2 2/2] phy: omap-usb2: Adapt phy-omap-usb2 for AM437x
Date: Tue, 15 Oct 2013 06:51:36 -0500 [thread overview]
Message-ID: <20131015115136.GB11380@radagast> (raw)
In-Reply-To: <1381820025-31376-3-git-send-email-george.cherian@ti.com>
[-- Attachment #1: Type: text/plain, Size: 3406 bytes --]
Hi,
On Tue, Oct 15, 2013 at 12:23:45PM +0530, George Cherian wrote:
> This patch adds a compatible for AM437x "ti,am43xx-usb2" to
> reuse the same phy-omap-usb2 driver.
it does more than just adding a new compatible flag.
> diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c
> index 3e5f08c..7c0bc6c 100644
> --- a/drivers/phy/phy-omap-usb2.c
> +++ b/drivers/phy/phy-omap-usb2.c
> @@ -144,6 +144,35 @@ static struct phy_ops ops = {
> .owner = THIS_MODULE,
> };
>
> +#ifdef CONFIG_OF
> +static const struct usb_phy_data omap_usb2_data = {
> + .label = "omap_usb2",
> + .set_host = omap_usb_set_host,
> + .set_peripheral = omap_usb_set_peripheral,
> + .set_vbus = omap_usb_set_vbus,
> + .start_srp = omap_usb_start_srp,
> +};
> +
> +static const struct usb_phy_data am437x_usb2_data = {
> + .label = "am437x_usb2",
> + .set_host = omap_usb_set_host,
> + .set_peripheral = omap_usb_set_peripheral,
> +};
> +
> +static const struct of_device_id omap_usb2_id_table[] = {
> + {
> + .compatible = "ti,omap-usb2",
> + .data = &omap_usb2_data,
> + },
> + {
> + .compatible = "ti,am437x-usb2",
> + .data = &am437x_usb2_data,
> + },
> + {},
> +};
> +MODULE_DEVICE_TABLE(of, omap_usb2_id_table);
> +#endif
> +
> static int omap_usb2_probe(struct platform_device *pdev)
> {
> struct omap_usb *phy;
> @@ -153,9 +182,14 @@ static int omap_usb2_probe(struct platform_device *pdev)
> struct device_node *node = pdev->dev.of_node;
> struct device_node *control_node;
> struct platform_device *control_pdev;
> + const struct of_device_id *of_id;
> + struct usb_phy_data *phy_data;
> +
> + of_id = of_match_device(of_match_ptr(omap_usb2_id_table), &pdev->dev);
>
> - if (!node)
> + if (!of_id)
> return -EINVAL;
> + phy_data = (struct usb_phy_data *)of_id->data;
>
> phy = devm_kzalloc(&pdev->dev, sizeof(*phy), GFP_KERNEL);
> if (!phy) {
> @@ -172,7 +206,7 @@ static int omap_usb2_probe(struct platform_device *pdev)
> phy->dev = &pdev->dev;
>
> phy->phy.dev = phy->dev;
> - phy->phy.label = "omap-usb2";
> + phy->phy.label = phy_data->label;
label can be set based on compatible flag:
if (of_device_is_compatible(node, "ti,omap-usb2"))
phy->phy.label = "omap-usb2";
else /* if (of_device_is_compatible(node, "ti,am437x-usb2")) */ /* default to newest */
phy->phy.label = "am437x-usb2"; /* keep name consistency */
> phy->phy.set_suspend = omap_usb2_suspend;
> phy->phy.otg = otg;
> phy->phy.type = USB_PHY_TYPE_USB2;
> @@ -199,10 +233,10 @@ static int omap_usb2_probe(struct platform_device *pdev)
> phy->is_suspended = 1;
> omap_control_usb_phy_power(phy->control_dev, 0);
>
> - otg->set_host = omap_usb_set_host;
> - otg->set_peripheral = omap_usb_set_peripheral;
> - otg->set_vbus = omap_usb_set_vbus;
> - otg->start_srp = omap_usb_start_srp;
> + otg->set_host = phy_data->set_host;
> + otg->set_peripheral = phy_data->set_peripheral;
> + otg->set_vbus = phy_data->set_vbus;
> + otg->start_srp = phy_data->start_srp;
this doesn't look right. I would rather have feature flags so that you
could:
if (test_bit(&phy_data->flags, OMAP_USB2_HAS_SRP))
otg->start_srp = omap_usb_start_srp;
and so on. Note that you might need to add __maybe_unused annotations to
those functions otherwise you'll get unused warnings.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-15 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 6:53 [PATCH v2 0/2] Adapt phy-omap-usb2 for AM437x platform George Cherian
2013-10-15 6:53 ` [PATCH v2 1/2] phy: omap-usb2: Arrange the include in alphabetical order George Cherian
2013-10-15 6:53 ` [PATCH v2 2/2] phy: omap-usb2: Adapt phy-omap-usb2 for AM437x George Cherian
2013-10-15 11:51 ` Felipe Balbi [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=20131015115136.GB11380@radagast \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=george.cherian@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kishon@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).