From: Roger Quadros <rogerq@ti.com>
To: Axel Lin <axel.lin@ingics.com>, Kishon Vijay Abraham I <kishon@ti.com>
Cc: Vignesh R <vigneshr@ti.com>, Felipe Balbi <balbi@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] phy: omap-control: Remove unneeded ifdef CONFIG_OF guard and of_match_ptr
Date: Thu, 5 Mar 2015 12:48:50 +0200 [thread overview]
Message-ID: <54F83492.5080103@ti.com> (raw)
In-Reply-To: <1425550725.21331.1.camel@phoenix>
Hi Alex,
On 05/03/15 12:18, Axel Lin wrote:
> if !CONFIG_OF, the probe fails.
> This is a dt-only driver, so the ifdef CONFIG_OF guard and of_match_ptr are
> not needed.
>
> Signed-off-by: Axel Lin <axel.lin@ingics.com>
> ---
> drivers/phy/phy-omap-control.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/phy/phy-omap-control.c b/drivers/phy/phy-omap-control.c
> index efe724f..a7653d9 100644
> --- a/drivers/phy/phy-omap-control.c
> +++ b/drivers/phy/phy-omap-control.c
> @@ -216,7 +216,6 @@ void omap_control_usb_set_mode(struct device *dev,
> return;
>
> ctrl_phy = dev_get_drvdata(dev);
> -
> if (!ctrl_phy) {
> dev_err(dev, "Invalid control phy device\n");
> return;
> @@ -241,8 +240,6 @@ void omap_control_usb_set_mode(struct device *dev,
> }
> EXPORT_SYMBOL_GPL(omap_control_usb_set_mode);
>
> -#ifdef CONFIG_OF
> -
> static const enum omap_control_phy_type otghs_data = OMAP_CTRL_TYPE_OTGHS;
> static const enum omap_control_phy_type usb2_data = OMAP_CTRL_TYPE_USB2;
> static const enum omap_control_phy_type pipe3_data = OMAP_CTRL_TYPE_PIPE3;
> @@ -278,8 +275,6 @@ static const struct of_device_id omap_control_phy_id_table[] = {
> {},
> };
> MODULE_DEVICE_TABLE(of, omap_control_phy_id_table);
> -#endif
> -
Since we're anyways going to fail probe for !CONFIG_OF, why do you want to
add the unnecessary device table to the kernel?
what are you benefiting from this change?
>
> static int omap_control_phy_probe(struct platform_device *pdev)
> {
> @@ -287,8 +282,7 @@ static int omap_control_phy_probe(struct platform_device *pdev)
> const struct of_device_id *of_id;
> struct omap_control_phy *control_phy;
>
> - of_id = of_match_device(of_match_ptr(omap_control_phy_id_table),
> - &pdev->dev);
> + of_id = of_match_device(omap_control_phy_id_table, &pdev->dev);
> if (!of_id)
> return -EINVAL;
>
> @@ -344,7 +338,7 @@ static struct platform_driver omap_control_phy_driver = {
> .probe = omap_control_phy_probe,
> .driver = {
> .name = "omap-control-phy",
> - .of_match_table = of_match_ptr(omap_control_phy_id_table),
> + .of_match_table = omap_control_phy_id_table,
> },
> };
>
>
cheers,
-roger
next prev parent reply other threads:[~2015-03-05 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 10:18 [PATCH 1/3] phy: omap-control: Remove unneeded ifdef CONFIG_OF guard and of_match_ptr Axel Lin
2015-03-05 10:20 ` [PATCH 2/3] phy: omap-usb2: " Axel Lin
2015-03-05 10:20 ` [PATCH 3/3] phy: ti-pipe3: " Axel Lin
2015-03-05 10:48 ` Roger Quadros [this message]
2015-03-05 15:29 ` [PATCH 1/3] phy: omap-control: " Axel Lin
2015-03-06 10:06 ` Roger Quadros
2015-03-09 5:11 ` Kishon Vijay Abraham I
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=54F83492.5080103@ti.com \
--to=rogerq@ti.com \
--cc=axel.lin@ingics.com \
--cc=balbi@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vigneshr@ti.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