From: paulius.zaleckas@gmail.com (Paulius Zaleckas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2 v2] S3C64XX: Fix 48M clock enable
Date: Tue, 12 Oct 2010 15:41:05 +0300 [thread overview]
Message-ID: <20101012123945.16469.2779.stgit@localhost.localdomain> (raw)
To enable 48M clock USB PHY must be initialized since 48M
is output of USB PHY PLL.
So fix a problem where other devices requiring 48M clock will
not work unless USB OTG driver is enabled.
is_osc was removed from OTG drivers platform data and implemented
as separate function s3c6400_clk_xusbxti_is_osc which should be
called from machine_init. Currently there is no in-kernel users
of it.
This fix is only for S3C64xx family, but I am sure something
similar will be needed for S5P family. I have started the work
but I am unable to finnish it since I only have datasheet for
S5PC100. Maybe Samsung guys could help me with this..?
However current patches doesn't break S5P since it is not
using s3c-hsotg driver (yet?).
---
Paulius Zaleckas (2):
USB: s3-hsotg: Remove PHY initialization code and use CLK API
[v2]ARM: S3C64XX: Fix USB and 48M clock enable procedure
arch/arm/mach-s3c64xx/clock.c | 67 ++++++++++++++++++-
arch/arm/plat-samsung/include/plat/clock.h | 2 +
arch/arm/plat-samsung/include/plat/udc-hs.h | 2 -
drivers/usb/gadget/s3c-hsotg.c | 94 +++++----------------------
4 files changed, 79 insertions(+), 86 deletions(-)
next reply other threads:[~2010-10-12 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 12:41 Paulius Zaleckas [this message]
2010-10-12 12:41 ` [PATCH 1/2] [v2]ARM: S3C64XX: Fix USB and 48M clock enable procedure Paulius Zaleckas
2010-10-12 12:41 ` [PATCH 2/2] USB: s3-hsotg: Remove PHY initialization code and use CLK API Paulius Zaleckas
2010-10-12 12:55 ` [PATCH 0/2 v2] S3C64XX: Fix 48M clock enable Marek Szyprowski
2010-10-12 13:49 ` Paulius Zaleckas
2010-10-12 14:15 ` Marek Szyprowski
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=20101012123945.16469.2779.stgit@localhost.localdomain \
--to=paulius.zaleckas@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 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).