From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Vivek Gautam <gautam.vivek@samsung.com>,
kgene.kim@samsung.com, l.majewski@samsung.com,
kyungmin.park@samsung.com, thomas.abraham@linaro.org,
linux-samsung-soc@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, m.szyprowski@samsung.com,
yulgon.kim@samsung.com, av.tikhomirov@samsung.com,
prashanth.g@samsung.com, boyko.lee@samsung.com,
joshi@samsung.com, a.kesavan@samsung.com, olofj@google.com,
ajaykumar.rs@samsung.com
Subject: Re: [PATCH 4/8 v2] ARM: EXYNOS5: Add EHCI device from device tree
Date: Thu, 26 Jul 2012 11:57:13 +0000 [thread overview]
Message-ID: <201207261157.14441.arnd@arndb.de> (raw)
In-Reply-To: <1342866729-30460-5-git-send-email-gautam.vivek@samsung.com>
On Saturday 21 July 2012, Vivek Gautam wrote:
> @@ -28,6 +29,11 @@ static struct exynos4_ohci_platdata smdk5250_ohci_pdata = {
> .phy_exit = s5p_usb_phy_exit,
> };
>
> +static struct s5p_ehci_platdata smdk5250_ehci_pdata = {
> + .phy_init = s5p_usb_phy_init,
> + .phy_exit = s5p_usb_phy_exit,
> +};
> +
> /*
> * The following lookup table is used to override device names when devices
> * are registered from device tree. This is temporarily added to enable
I'm a bit confused of the purpose of setting the function pointers here
when the pointers are always to the same s5p_usb_phy_init/s5p_usb_phy_exit
identifiers, but you have different definitions of those functions
depending on which platforms you are building for.
What is the idea here? Are you going to unify the three definitions of
s5p_usb_phy_init, or is that function going away eventually when we
get to the point of building exynos/s5p/s3c64xx into the same kernel
binary?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/8 v2] ARM: EXYNOS5: Add EHCI device from device tree
Date: Thu, 26 Jul 2012 11:57:13 +0000 [thread overview]
Message-ID: <201207261157.14441.arnd@arndb.de> (raw)
In-Reply-To: <1342866729-30460-5-git-send-email-gautam.vivek@samsung.com>
On Saturday 21 July 2012, Vivek Gautam wrote:
> @@ -28,6 +29,11 @@ static struct exynos4_ohci_platdata smdk5250_ohci_pdata = {
> .phy_exit = s5p_usb_phy_exit,
> };
>
> +static struct s5p_ehci_platdata smdk5250_ehci_pdata = {
> + .phy_init = s5p_usb_phy_init,
> + .phy_exit = s5p_usb_phy_exit,
> +};
> +
> /*
> * The following lookup table is used to override device names when devices
> * are registered from device tree. This is temporarily added to enable
I'm a bit confused of the purpose of setting the function pointers here
when the pointers are always to the same s5p_usb_phy_init/s5p_usb_phy_exit
identifiers, but you have different definitions of those functions
depending on which platforms you are building for.
What is the idea here? Are you going to unify the three definitions of
s5p_usb_phy_init, or is that function going away eventually when we
get to the point of building exynos/s5p/s3c64xx into the same kernel
binary?
Arnd
next prev parent reply other threads:[~2012-07-26 21:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-21 10:32 [PATCH 0/8 v2] EXYNOS5: USB: Add USB 2.0 and USB 3.0 support for exynos5 Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 1/8 v2] EXYNOS4: USB: Generalising setup-usb-phy driver for exynos Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 2/8 v2] ARM: EXYNOS5: Add machine data for USB 2.0 Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-26 11:24 ` Arnd Bergmann
2012-07-26 11:24 ` Arnd Bergmann
2012-07-28 16:05 ` Vivek Gautam
2012-07-28 16:05 ` Vivek Gautam
2012-07-29 13:11 ` Arnd Bergmann
2012-07-29 13:11 ` Arnd Bergmann
2012-08-01 3:02 ` Joonyoung Shim
2012-08-01 3:02 ` Joonyoung Shim
2012-07-21 10:32 ` [PATCH 3/8 v2] ARM: EXYNOS5: Add OHCI device from device tree Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 4/8 v2] ARM: EXYNOS5: Add EHCI " Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-26 11:57 ` Arnd Bergmann [this message]
2012-07-26 11:57 ` Arnd Bergmann
2012-07-28 16:41 ` Vivek Gautam
2012-07-28 16:42 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 5/8 v2] ARM: EXYNOS5: Add PHY initialization code for usb 2.0 Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
[not found] ` <1342866729-30460-6-git-send-email-gautam.vivek-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2012-07-26 12:08 ` Arnd Bergmann
2012-07-26 12:08 ` Arnd Bergmann
2012-07-21 10:32 ` [PATCH 6/8 v2] ARM: EXYNOS5: Add machine data for USB3.0 Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 7/8 v2] ARM: EXYNOS5: Add XHCI device from device tree Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
2012-07-21 10:32 ` [PATCH 8/8 v2] ARM: EXYNOS5: Add PHY initialization code for usb 3.0 Vivek Gautam
2012-07-21 10:32 ` Vivek Gautam
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=201207261157.14441.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=a.kesavan@samsung.com \
--cc=ajaykumar.rs@samsung.com \
--cc=av.tikhomirov@samsung.com \
--cc=boyko.lee@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gautam.vivek@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=l.majewski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=olofj@google.com \
--cc=prashanth.g@samsung.com \
--cc=thomas.abraham@linaro.org \
--cc=yulgon.kim@samsung.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 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.