From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Scott Branden <scott.branden@broadcom.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Ray Jui <rjui@broadcom.com>
Subject: Re: [PATCH] Input: set default for iProc touchscreen
Date: Tue, 11 Oct 2016 10:49:49 -0700 [thread overview]
Message-ID: <20161011174949.GA8841@dtor-ws> (raw)
In-Reply-To: <1475950295-9660-1-git-send-email-scott.branden@broadcom.com>
On Sat, Oct 08, 2016 at 11:11:35AM -0700, Scott Branden wrote:
> Enable the Broadcom iProc touchscreen by default for all iProc platforms.
Why? Not all of them will have touchscreen attached, will they?
Thanks.
>
> Signed-off-by: Ray Jui <rjui@broadcom.com>
> Signed-off-by: Scott Branden <scott.branden@broadcom.com>
> ---
> drivers/input/touchscreen/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/input/touchscreen/Kconfig b/drivers/input/touchscreen/Kconfig
> index 2fb1f43..f785371 100644
> --- a/drivers/input/touchscreen/Kconfig
> +++ b/drivers/input/touchscreen/Kconfig
> @@ -364,6 +364,7 @@ config TOUCHSCREEN_ILI210X
> config TOUCHSCREEN_IPROC
> tristate "IPROC touch panel driver support"
> depends on ARCH_BCM_IPROC || COMPILE_TEST
> + default ARCH_BCM_IPROC
> help
> Say Y here if you want to add support for the IPROC touch
> controller to your system.
> --
> 2.5.0
>
--
Dmitry
next prev parent reply other threads:[~2016-10-11 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 18:11 [PATCH] Input: set default for iProc touchscreen Scott Branden
2016-10-11 17:49 ` Dmitry Torokhov [this message]
2016-10-11 18:58 ` Scott Branden
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=20161011174949.GA8841@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=scott.branden@broadcom.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.