From: tushar.behera@linaro.org (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: dts: Add EHCI device tree node for Exynos4
Date: Mon, 31 Dec 2012 09:09:22 +0530 [thread overview]
Message-ID: <50E108EA.1010404@linaro.org> (raw)
In-Reply-To: <1356921918-12959-1-git-send-email-tobetter@gmail.com>
On 12/31/2012 08:15 AM, Dongjin Kim wrote:
> This patch adds EHCI device node on device tree for Exynos4 and defines its
> default platform data, s5p_usb_phy_init and s5p_usb_phy_exit, so that those
> function can be called from the driver.
>
> Signed-off-by: Dongjin Kim <tobetter@gmail.com>
> ---
> arch/arm/boot/dts/exynos4.dtsi | 7 +++++++
> arch/arm/mach-exynos/mach-exynos4-dt.c | 9 +++++++++
> 2 files changed, 16 insertions(+)
[ ... ]
>
> +static struct s5p_ehci_platdata s5p_ehci_platdata = {
> + .phy_init = s5p_usb_phy_init,
> + .phy_exit = s5p_usb_phy_exit,
> +};
> +
Going by the recent development on Samsung USBPHY driver, we won't need
these hooks once that patch gets accepted. [1]
Patch for adding EHCI support for EXYNOS5-DT can be found here.[2]
[1] https://patchwork.kernel.org/patch/1794651/
[2] https://patchwork.kernel.org/patch/1875491/
> /*
> * The following lookup table is used to override device names when devices
> * are registered from device tree. This is temporarily added to enable
> @@ -80,6 +87,8 @@ static const struct of_dev_auxdata exynos4_auxdata_lookup[] __initconst = {
> OF_DEV_AUXDATA("arm,pl330", EXYNOS4_PA_MDMA1, "dma-pl330.2", NULL),
> OF_DEV_AUXDATA("samsung,exynos4210-tmu", EXYNOS4_PA_TMU,
> "exynos-tmu", NULL),
> + OF_DEV_AUXDATA("samsung,exynos-ehci", EXYNOS4_PA_EHCI,
> + "s5p-ehci", &s5p_ehci_platdata),
> {},
> };
>
>
--
Tushar Behera
prev parent reply other threads:[~2012-12-31 3:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 2:45 [PATCH RESEND] ARM: dts: Add EHCI device tree node for Exynos4 Dongjin Kim
2012-12-31 3:39 ` Tushar Behera [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=50E108EA.1010404@linaro.org \
--to=tushar.behera@linaro.org \
--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).