From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Thomas Abraham' <thomas.abraham@linaro.org>,
linux-samsung-soc@vger.kernel.org
Cc: linux-input@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] arm: exynos4: fix incorrect pad configuration for keypad row lines
Date: Thu, 15 Sep 2011 14:52:18 +0900 [thread overview]
Message-ID: <00a201cc736b$a11dc740$e35955c0$%kim@samsung.com> (raw)
In-Reply-To: <1315129244-26489-1-git-send-email-thomas.abraham@linaro.org>
Thomas Abraham wrote:
>
> The keypad controller requires a external pull-up for all the keypad
> row lines. Fix the incorrect pad configuration for keypad controller
> row lines by enabling the pad pull-up for the all row lines of the
> keypad controller.
>
> Signed-off-by: Thomas Abraham <thomas.abraham@linaro.org>
> ---
> SMDKV310 board does not have pull-up resistors populated for the keypad
> row lines (unlike the smdk boards for the previous Samsung SoC's). So
> the pad pull-up for all keypad row lines should be enabled for
> smdkv310 board.
>
> The default requirement for the keypad controller is to enable the
> pull-up for all the keypad row lines. If a exynos4 based board has
> on-board pull-up's populated for keypad row lines, this patch would
> cause no harm. And in such cases, if internal pad pull-up is to be
> disabled (to reduce some power consumption), an alternative gpio
> configuration function can be supplied that does not enable the
> internal pad pull-up.
> ---
> arch/arm/mach-exynos4/setup-keypad.c | 11 ++++++-----
> 1 files changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm/mach-exynos4/setup-keypad.c b/arch/arm/mach-
> exynos4/setup-keypad.c
> index 1ee0ebf..7862bfb 100644
> --- a/arch/arm/mach-exynos4/setup-keypad.c
> +++ b/arch/arm/mach-exynos4/setup-keypad.c
> @@ -19,15 +19,16 @@ void samsung_keypad_cfg_gpio(unsigned int rows,
> unsigned int cols)
>
> if (rows > 8) {
> /* Set all the necessary GPX2 pins: KP_ROW[0~7] */
> - s3c_gpio_cfgrange_nopull(EXYNOS4_GPX2(0), 8,
> S3C_GPIO_SFN(3));
> + s3c_gpio_cfgall_range(EXYNOS4_GPX2(0), 8,
> S3C_GPIO_SFN(3),
> + S3C_GPIO_PULL_UP);
>
> /* Set all the necessary GPX3 pins: KP_ROW[8~] */
> - s3c_gpio_cfgrange_nopull(EXYNOS4_GPX3(0), (rows - 8),
> - S3C_GPIO_SFN(3));
> + s3c_gpio_cfgall_range(EXYNOS4_GPX3(0), (rows - 8),
> + S3C_GPIO_SFN(3),
> S3C_GPIO_PULL_UP);
> } else {
> /* Set all the necessary GPX2 pins: KP_ROW[x] */
> - s3c_gpio_cfgrange_nopull(EXYNOS4_GPX2(0), rows,
> - S3C_GPIO_SFN(3));
> + s3c_gpio_cfgall_range(EXYNOS4_GPX2(0), rows,
> S3C_GPIO_SFN(3),
> + S3C_GPIO_PULL_UP);
> }
>
> /* Set all the necessary GPX1 pins to special-function 3: KP_COL[x]
*/
> --
> 1.6.6.rc2
Oops, you're right, applied.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2011-09-15 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 9:40 [PATCH] arm: exynos4: fix incorrect pad configuration for keypad row lines Thomas Abraham
2011-09-04 9:53 ` Alan Cox
2011-09-04 10:37 ` Thomas Abraham
2011-09-15 5:52 ` Kukjin Kim [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='00a201cc736b$a11dc740$e35955c0$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thomas.abraham@linaro.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).