From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Wan ZongShun <mcuos.com@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Baruch Siach <baruch@tkos.co.il>,
linux-arm-kernel <linux-arm-kernel@lists.arm.linux.org.uk>,
linux-input@vger.kernel.org, Trilok Soni <soni.trilok@gmail.com>
Subject: Re: [PATCH v2] input:Add clk api support for w90p910 touchscreen
Date: Thu, 9 Jul 2009 10:06:06 +0100 [thread overview]
Message-ID: <20090709090606.GA30597@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4A55B1B7.3090802@gmail.com>
On Thu, Jul 09, 2009 at 05:00:39PM +0800, Wan ZongShun wrote:
> Dear Dmitry,
>
> >>> Umm, one more thing - we need to add "depends on" to Kconfig since
> >>> clk API is not implemented on every platform. Any ideas what is the
> >>> most wide dependency is?
> >> The most wide dependency for the clk API is HAVE_CLK.
> >>
> >
> > Cool, thanks.
> >
> Sure, but why to add it to touchscreen's kconfig?
> it seems it should be put arch/arm/kconfig.
>
> In addition,I never use this HAVE_CLK in ARCH_W90X900,
> only using COMMON_CLKDEV to support clk API.
HAVE_CLK is the configuration symbol which tells the rest of the kernel
configuration system that the clk API is available. Drivers using the
clk API should depend on HAVE_CLK.
COMMON_CLKDEV is just one implementation of a subset of the clk API, and
nothing should ever depend on this symbol.
next prev parent reply other threads:[~2009-07-09 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 2:53 [PATCH v2] input:Add clk api support for w90p910 touchscreen Wan ZongShun
2009-07-09 5:11 ` Dmitry Torokhov
2009-07-09 5:14 ` Wan ZongShun
2009-07-09 6:29 ` Dmitry Torokhov
2009-07-09 7:01 ` Wan ZongShun
2009-07-09 7:37 ` Baruch Siach
2009-07-09 8:54 ` Dmitry Torokhov
2009-07-09 9:00 ` Wan ZongShun
2009-07-09 9:06 ` Russell King - ARM Linux [this message]
2009-07-09 9:23 ` Wan ZongShun
2009-07-11 15:33 ` Russell King - ARM Linux
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=20090709090606.GA30597@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=baruch@tkos.co.il \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=mcuos.com@gmail.com \
--cc=soni.trilok@gmail.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 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).