From: varkabhadram@gmail.com (Varka Bhadram)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 05/12] phy: add the Berlin USB PHY driver
Date: Wed, 16 Jul 2014 15:03:14 +0530 [thread overview]
Message-ID: <53C646DA.3020002@gmail.com> (raw)
In-Reply-To: <20140716092541.GC28151@kwain>
On 07/16/2014 02:55 PM, Antoine T?nart wrote:
> Hi Varka,
>
> On Wed, Jul 16, 2014 at 02:49:05PM +0530, Varka Bhadram wrote:
>> On 07/16/2014 01:55 PM, Antoine T?nart wrote:
>>> +static const struct of_device_id phy_berlin_sata_of_match[] = {
>>> + {
>>> + .compatible = "marvell,berlin2-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[0],
>>> + },
>>> + {
>>> + .compatible = "marvell,berlin2cd-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[1],
>>> + },
>>> + { },
>>> +};
>>> +MODULE_DEVICE_TABLE(of, phy_berlin_sata_of_match);
>>> +
>> It looks good if we move this after probe().. So that we can see of_match_table directly...
> We use the of match table in the probe, when calling of_match_device().
>
>>> +static int phy_berlin_usb_probe(struct platform_device *pdev)
>>> +{
>>> + const struct of_device_id *match =
>>> + of_match_device(phy_berlin_sata_of_match, &pdev->dev);
We are updating of_match_table in platform_driver struct.
Every driver follows the concept of giving the of_device_ids
above the platform_driver declaration...
> Here.
>
> Antoine
>
WARNING: multiple messages have this Message-ID (diff)
From: Varka Bhadram <varkabhadram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Antoine Ténart"
<antoine.tenart-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Peter.Chen-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
balbi-l0cyMroinI0@public.gmane.org,
p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
thomas.petazzoni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org,
zmxu-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org,
jszhang-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v3 05/12] phy: add the Berlin USB PHY driver
Date: Wed, 16 Jul 2014 15:03:14 +0530 [thread overview]
Message-ID: <53C646DA.3020002@gmail.com> (raw)
In-Reply-To: <20140716092541.GC28151@kwain>
On 07/16/2014 02:55 PM, Antoine Ténart wrote:
> Hi Varka,
>
> On Wed, Jul 16, 2014 at 02:49:05PM +0530, Varka Bhadram wrote:
>> On 07/16/2014 01:55 PM, Antoine Ténart wrote:
>>> +static const struct of_device_id phy_berlin_sata_of_match[] = {
>>> + {
>>> + .compatible = "marvell,berlin2-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[0],
>>> + },
>>> + {
>>> + .compatible = "marvell,berlin2cd-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[1],
>>> + },
>>> + { },
>>> +};
>>> +MODULE_DEVICE_TABLE(of, phy_berlin_sata_of_match);
>>> +
>> It looks good if we move this after probe().. So that we can see of_match_table directly...
> We use the of match table in the probe, when calling of_match_device().
>
>>> +static int phy_berlin_usb_probe(struct platform_device *pdev)
>>> +{
>>> + const struct of_device_id *match =
>>> + of_match_device(phy_berlin_sata_of_match, &pdev->dev);
We are updating of_match_table in platform_driver struct.
Every driver follows the concept of giving the of_device_ids
above the platform_driver declaration...
> Here.
>
> Antoine
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Varka Bhadram <varkabhadram@gmail.com>
To: "Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: sebastian.hesselbarth@gmail.com, Peter.Chen@freescale.com,
balbi@ti.com, p.zabel@pengutronix.de,
alexandre.belloni@free-electrons.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
jszhang@marvell.com, linux-arm-kernel@lists.infradead.org,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 05/12] phy: add the Berlin USB PHY driver
Date: Wed, 16 Jul 2014 15:03:14 +0530 [thread overview]
Message-ID: <53C646DA.3020002@gmail.com> (raw)
In-Reply-To: <20140716092541.GC28151@kwain>
On 07/16/2014 02:55 PM, Antoine Ténart wrote:
> Hi Varka,
>
> On Wed, Jul 16, 2014 at 02:49:05PM +0530, Varka Bhadram wrote:
>> On 07/16/2014 01:55 PM, Antoine Ténart wrote:
>>> +static const struct of_device_id phy_berlin_sata_of_match[] = {
>>> + {
>>> + .compatible = "marvell,berlin2-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[0],
>>> + },
>>> + {
>>> + .compatible = "marvell,berlin2cd-usb-phy",
>>> + .data = &phy_berlin_pll_dividers[1],
>>> + },
>>> + { },
>>> +};
>>> +MODULE_DEVICE_TABLE(of, phy_berlin_sata_of_match);
>>> +
>> It looks good if we move this after probe().. So that we can see of_match_table directly...
> We use the of match table in the probe, when calling of_match_device().
>
>>> +static int phy_berlin_usb_probe(struct platform_device *pdev)
>>> +{
>>> + const struct of_device_id *match =
>>> + of_match_device(phy_berlin_sata_of_match, &pdev->dev);
We are updating of_match_table in platform_driver struct.
Every driver follows the concept of giving the of_device_ids
above the platform_driver declaration...
> Here.
>
> Antoine
>
next prev parent reply other threads:[~2014-07-16 9:33 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 8:25 [PATCH v3 00/12] ARM: berlin: USB support Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` [PATCH v3 01/12] reset: add the Berlin reset controller driver Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 16:39 ` Andrew Lunn
2014-07-16 16:39 ` Andrew Lunn
2014-07-16 16:39 ` Andrew Lunn
2014-07-16 8:25 ` [PATCH v3 02/12] Documentation: bindings: add reset bindings docs for Marvell Berlin SoCs Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` [PATCH v3 03/12] ARM: Berlin: select the reset controller Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` [PATCH v3 04/12] ARM: dts: berlin: add a required reset property in the chip controller node Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` [PATCH v3 05/12] phy: add the Berlin USB PHY driver Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 8:25 ` Antoine Ténart
2014-07-16 9:19 ` Varka Bhadram
2014-07-16 9:19 ` Varka Bhadram
2014-07-16 9:19 ` Varka Bhadram
2014-07-16 9:25 ` Antoine Ténart
2014-07-16 9:25 ` Antoine Ténart
2014-07-16 9:25 ` Antoine Ténart
2014-07-16 9:33 ` Varka Bhadram [this message]
2014-07-16 9:33 ` Varka Bhadram
2014-07-16 9:33 ` Varka Bhadram
2014-07-16 9:47 ` Antoine Ténart
2014-07-16 9:47 ` Antoine Ténart
2014-07-16 9:50 ` Varka Bhadram
2014-07-16 9:50 ` Varka Bhadram
2014-07-16 8:26 ` [PATCH v3 06/12] Documentation: bindings: add doc for the Berlin USB PHY Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` [PATCH v3 07/12] usb: chipidea: add a usb2 driver for ci13xxx Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:41 ` Arnd Bergmann
2014-07-16 8:41 ` Arnd Bergmann
2014-07-16 8:41 ` Arnd Bergmann
2014-07-16 9:15 ` Antoine Ténart
2014-07-16 9:15 ` Antoine Ténart
2014-07-16 9:15 ` Antoine Ténart
2014-07-16 10:14 ` Arnd Bergmann
2014-07-16 10:14 ` Arnd Bergmann
2014-07-16 10:14 ` Arnd Bergmann
2014-07-16 11:58 ` Peter Chen
2014-07-16 11:58 ` Peter Chen
2014-07-16 12:12 ` Arnd Bergmann
2014-07-16 12:12 ` Arnd Bergmann
2014-07-16 12:12 ` Arnd Bergmann
2014-07-17 1:20 ` Peter Chen
2014-07-17 1:20 ` Peter Chen
2014-07-17 1:20 ` Peter Chen
2014-07-17 10:21 ` Arnd Bergmann
2014-07-17 10:21 ` Arnd Bergmann
2014-07-17 10:21 ` Arnd Bergmann
2014-07-17 11:19 ` Peter Chen
2014-07-17 11:19 ` Peter Chen
2014-07-17 11:19 ` Peter Chen
2014-07-17 11:34 ` Arnd Bergmann
2014-07-17 11:34 ` Arnd Bergmann
2014-07-17 12:20 ` Russell King - ARM Linux
2014-07-17 12:20 ` Russell King - ARM Linux
2014-07-25 2:18 ` Peter Chen
2014-07-25 2:18 ` Peter Chen
2014-07-25 2:18 ` Peter Chen
2014-07-25 8:07 ` Antoine Ténart
2014-07-25 8:07 ` Antoine Ténart
2014-07-25 8:07 ` Antoine Ténart
2014-07-25 8:22 ` Peter Chen
2014-07-25 8:22 ` Peter Chen
2014-07-16 8:26 ` [PATCH v3 08/12] Documentation: bindings: add doc for the USB2 ChipIdea USB driver Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:39 ` Arnd Bergmann
2014-07-16 8:39 ` Arnd Bergmann
2014-07-16 8:39 ` Arnd Bergmann
2014-07-16 8:59 ` Antoine Ténart
2014-07-16 8:59 ` Antoine Ténart
2014-07-16 8:26 ` [PATCH v3 09/12] ARM: dts: berlin: add BG2Q nodes for USB support Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` [PATCH v3 10/12] ARM: dts: Berlin: enable USB on the BG2Q DMP Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` [PATCH v3 11/12] ARM: dts: berlin: add BG2CD nodes for USB support Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
2014-07-16 8:26 ` [PATCH v3 12/12] ARM: dts: berlin: enable USB on the Google Chromecast Antoine Ténart
2014-07-16 8:26 ` Antoine Ténart
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=53C646DA.3020002@gmail.com \
--to=varkabhadram@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.