From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
linux-samsung-soc@vger.kernel.org
Cc: k.kozlowski.k@gmail.com, Kukjin Kim <kgene@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Subject: Re: [PATCH] ARM: dts: exynos5422-odroidxu3*: use peripheral mode for dwc3_1
Date: Thu, 19 Nov 2015 21:33:17 +0900 [thread overview]
Message-ID: <564DC18D.3000700@samsung.com> (raw)
In-Reply-To: <1447933882-3030-1-git-send-email-m.szyprowski@samsung.com>
W dniu 19.11.2015 o 20:51, Marek Szyprowski pisze:
> DWC3 device found on Exynos SoCs cannot work in OTG mode alone, because
> it lacks some OTG related control part. OTG mode operation is possible
> only with external hardware logic (usually GPIO-based) specific to
> the board. Right now, however, there is no driver for such logic and no
> bindings, so the OTG mode is disfunctional at all (this means that it
s/disfunctional/dysfunctional/
(no need to resend, this can be fixed when applying)
> doesn't work as a peripheral nor as a host). This patch sets the operation
> mode to peripheral to get DWC3_1 device at least somehow working. This can
> be later updated, when proper OTG driver and bindings get developed.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> arch/arm/boot/dts/exynos5422-odroidxu3-lite.dts | 2 +-
> arch/arm/boot/dts/exynos5422-odroidxu3.dts | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
Explanation makes sense.
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2015-11-19 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 11:51 [PATCH] ARM: dts: exynos5422-odroidxu3*: use peripheral mode for dwc3_1 Marek Szyprowski
2015-11-19 12:33 ` Krzysztof Kozlowski [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=564DC18D.3000700@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@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.