public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v8 1/2] S5P: Exynos: Add GPIO pin numbering and rename definitions
Date: Wed, 16 Apr 2014 20:38:44 +0900	[thread overview]
Message-ID: <534E6BC4.2000008@samsung.com> (raw)
In-Reply-To: <1397626357-6091-2-git-send-email-akshay.s@samsung.com>

Hi, Akshay.

Did you test exynos4 board?
I have tested your patch-set with the exynos4 board(TRATS2).
It didn't work. 

Occurred DATA_ABORT.
gpio_set_pull(EXYNOS4x12_GPIO_X15,...);

Add the comment at below.

On 04/16/2014 02:32 PM, Akshay Saraswat wrote:
> This patch includes following changes :
> * Adds gpio pin numbering support for EXYNOS SOCs.
>   To have consistent 0..n-1 GPIO numbering the banks are divided
>   into different parts where ever they have holes in them.
> 
> * Rename GPIO definitions from GPIO_... to S5P_GPIO_...
>   These changes were done to enable cmd_gpio for EXYNOS and
>   cmd_gpio has GPIO_INPUT same as s5p_gpio driver and hence
>   getting a error during compilation.
> 
> * Adds support for name to gpio conversion in s5p_gpio to enable
>   gpio command EXYNOS SoCs. Function has been added to asm/gpio.h
>   to decode the input gpio name to gpio number.
>   Example: SMDK5420 # gpio set gpa00
> 
> Signed-off-by: Leela Krishna Amudala <l.krishna@samsung.com>
> Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com>
> Signed-off-by: Akshay Saraswat <akshay.s@samsung.com>
> ---
>  arch/arm/cpu/armv7/exynos/pinmux.c       |  403 +++----
>  arch/arm/include/asm/arch-exynos/cpu.h   |   17 +-
>  arch/arm/include/asm/arch-exynos/gpio.h  | 1778 +++++++++++++++++++++++++-----
>  arch/arm/include/asm/arch-s5pc1xx/gpio.h |  941 +++++++++++++---
>  board/samsung/arndale/arndale.c          |   11 +-
>  board/samsung/goni/goni.c                |   26 +-
>  board/samsung/smdk5250/exynos5-dt.c      |   20 +-
>  board/samsung/smdk5250/smdk5250.c        |   19 +-
>  board/samsung/smdk5420/smdk5420.c        |   15 +-
>  board/samsung/smdkc100/smdkc100.c        |    5 +-
>  board/samsung/smdkv310/smdkv310.c        |   17 +-
>  board/samsung/trats/trats.c              |   39 +-
>  board/samsung/trats2/trats2.c            |   74 +-
>  board/samsung/universal_c210/universal.c |   51 +-
>  drivers/gpio/s5p_gpio.c                  |  194 +++-
>  15 files changed, 2779 insertions(+), 831 deletions(-)
> 
> diff --git a/arch/arm/cpu/armv7/exynos/pinmux.c b/arch/arm/cpu/armv7/exynos/pinmux.c
> index 9edb475..e26eb51 100644
> --- a/arch/arm/cpu/armv7/exynos/pinmux.c
> +++ b/arch/arm/cpu/armv7/exynos/pinmux.c
> @@ -13,30 +13,23 @@

[..snip..]

> -
> +#if 0
>  /* functions */
>  void s5p_gpio_cfg_pin(struct s5p_gpio_bank *bank, int gpio, int cfg);
>  void s5p_gpio_direction_output(struct s5p_gpio_bank *bank, int gpio, int en);
> @@ -244,6 +29,7 @@ unsigned int s5p_gpio_get_value(struct s5p_gpio_bank *bank, int gpio);
>  void s5p_gpio_set_pull(struct s5p_gpio_bank *bank, int gpio, int mode);
>  void s5p_gpio_set_drv(struct s5p_gpio_bank *bank, int gpio, int mode);
>  void s5p_gpio_set_rate(struct s5p_gpio_bank *bank, int gpio, int mode);
> +#endif

Why did you use the "#if 0 ~ #endif".
If it didn't need to use, it can be removed, isn't?

Best Regards,
Jaehoon Chung

  reply	other threads:[~2014-04-16 11:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16  5:32 [U-Boot] [PATCH v8 0/2] Exynos5: Add GPIO numbering feature Akshay Saraswat
2014-04-16  5:32 ` [U-Boot] [PATCH v8 1/2] S5P: Exynos: Add GPIO pin numbering and rename definitions Akshay Saraswat
2014-04-16 11:38   ` Jaehoon Chung [this message]
2014-04-16 12:17   ` Przemyslaw Marczak
2014-04-16  5:32 ` [U-Boot] [PATCH v8 2/2] S5P: Exynos: Config: Enable Generic GPIO and CMD configs Akshay Saraswat
  -- strict thread matches above, loose matches on Subject: below --
2014-04-16 13:20 [U-Boot] [PATCH v8 1/2] S5P: Exynos: Add GPIO pin numbering and rename definitions Akshay Saraswat
2014-04-16 13:47 ` Przemyslaw Marczak
2014-04-16 13:27 Akshay Saraswat
2014-04-16 13:48 ` Przemyslaw Marczak
2014-04-16 14:48   ` Simon Glass
2014-04-16 14:59     ` Przemyslaw Marczak

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=534E6BC4.2000008@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=u-boot@lists.denx.de \
    /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