linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC/RFT] ARM: S5P: Fix USB and 48M clock enable procedure
Date: Thu, 14 Oct 2010 18:03:52 +0900	[thread overview]
Message-ID: <008001cb6b7e$ba952920$2fbf7b60$%kim@samsung.com> (raw)
In-Reply-To: <20101012194021.11514.12704.stgit@localhost.localdomain>

Paulius Zaleckas wrote:
> 
> Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com>
> ---
> 
>  arch/arm/mach-s5p6440/clock.c              |   23 -------
>  arch/arm/plat-s5p/clock.c                  |   86
> ++++++++++++++++++++++++++++
>  arch/arm/plat-s5p/include/plat/s5p-clock.h |    1
>  3 files changed, 86 insertions(+), 24 deletions(-)
> 
Hi Paulius,

There are some comments about your patches which includes previous S3C64XX patches.

Basically your approach looks good trial and structure...but I'm not sure whether your approach can be used commonly on Samsung's all SoCs or not.
Need to do more test on boards and I already informed your patches to USB engineers in my team, actually need to discuss about this.

As a note, I know, 'xusbxti' clock is structure for external xtal which is used for generating USB clock on board... it depends on board condition, because can be used 12/24/48Mhz on board. The clk_48m means generated actual USB clock, 48Mhz. So should be implemented enable function by using clk_48m...

Anyway let you know about the result of internal discussion soon, then let's talk.

Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

  reply	other threads:[~2010-10-14  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-12 19:40 [PATCH RFC/RFT] ARM: S5P: Fix USB and 48M clock enable procedure Paulius Zaleckas
2010-10-14  9:03 ` Kukjin Kim [this message]
2010-10-14 14:19   ` Paulius Zaleckas
2010-10-15 12:56     ` Kukjin Kim
2010-10-15 16:12       ` Paulius Zaleckas

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='008001cb6b7e$ba952920$2fbf7b60$%kim@samsung.com' \
    --to=kgene.kim@samsung.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).