Eunki Kim wrote:
When a device uses GPIO interrupt, its driver assumes that GPIO
should be INPUT mode. However, GPIO of SAMSUNG SoC is sepated to
INPUT mode and INTERRUPT mode. They are set by 0x0 and 0xF in GPIO
control register. If the register is set to INPUT mode, the
interrupt never
...@linaro.org; kgene@samsung.com
Subject: Re: [PATCH 1/2] ARM: SAMSUNG: Insert bitmap_gpio_int member in
samsung_gpio_chip
On 09/27/2012 12:55 PM, Eunki Kim wrote:
When a device uses GPIO interrupt, its driver assumes that GPIO should
be INPUT mode. However, GPIO of SAMSUNG SoC is sepated
Subject: Re: [PATCH 1/2] ARM: SAMSUNG: Insert bitmap_gpio_int member in
samsung_gpio_chip
On 09/27/2012 02:55 PM, Eunki Kim wrote:
-Original Message-
From: Joonyoung Shim [mailto:jy0922.s...@samsung.com]
Sent: Thursday, September 27, 2012 1:50 PM
To: Eunki Kim
Cc: linux-arm-ker
When a device uses GPIO interrupt, its driver assumes that GPIO
should be INPUT mode. However, GPIO of SAMSUNG SoC is sepated to
INPUT mode and INTERRUPT mode. They are set by 0x0 and 0xF in GPIO
control register. If the register is set to INPUT mode, the
interrupt never occur. Therefore, it's
On 09/27/2012 12:55 PM, Eunki Kim wrote:
When a device uses GPIO interrupt, its driver assumes that GPIO
should be INPUT mode. However, GPIO of SAMSUNG SoC is sepated to
INPUT mode and INTERRUPT mode. They are set by 0x0 and 0xF in GPIO
control register. If the register is set to INPUT mode, the
Subject: Re: [PATCH 1/2] ARM: SAMSUNG: Insert bitmap_gpio_int member in
samsung_gpio_chip
On 09/27/2012 12:55 PM, Eunki Kim wrote:
When a device uses GPIO interrupt, its driver assumes that GPIO should
be INPUT mode. However, GPIO of SAMSUNG SoC is sepated to INPUT mode
and INTERRUPT mode
