From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] omap5: Configure the tca6424 gpio expander
Date: Mon, 8 Jul 2013 16:19:34 -0500 [thread overview]
Message-ID: <51DB2CE6.3060808@ti.com> (raw)
In-Reply-To: <1373316840-28436-2-git-send-email-dmurphy@ti.com>
$subject
omap5: uevm
On 07/08/2013 03:54 PM, Dan Murphy wrote:
> Configure the tca6424 gpio expander
> This allows use of the debug and tri color LEDs.
> As well as HDMI PEO signal.
we use HDMI in u-boot?
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
> board/ti/omap5_uevm/evm.c | 12 ++++++++++++
> board/ti/omap5_uevm/mux_data.h | 2 ++
> include/configs/omap5_uevm.h | 5 +++++
> 3 files changed, 19 insertions(+)
>
> diff --git a/board/ti/omap5_uevm/evm.c b/board/ti/omap5_uevm/evm.c
> index 90046e8..ee96ae1 100644
> --- a/board/ti/omap5_uevm/evm.c
> +++ b/board/ti/omap5_uevm/evm.c
> @@ -26,6 +26,7 @@
> #include <palmas.h>
> #include <asm/arch/sys_proto.h>
> #include <asm/arch/mmc_host_def.h>
> +#include <tca642x.h>
>
> #include "mux_data.h"
>
> @@ -35,6 +36,15 @@ const struct omap_sysinfo sysinfo = {
> "Board: OMAP5430 EVM\n"
> };
>
> +/* Initial states for the GPIO expander
Doc comment style.
> + * input reg, output reg, polarity reg, configuration reg
> + */
> +struct tca642x_bank_info tca642x_init[] = {
> + {0x00, 0x04, 0x00, 0x80},
> + {0x00, 0x00, 0x00, 0xff},
> + {0x00, 0x00, 0x00, 0x40},
could you be explicit and use .input_reg = etc?
btw, why should board know about input_reg, output_reg polarity_reg?
is'nt that the job of the driver?
> +};
> +
> /**
> * @brief board_init
> *
> @@ -46,6 +56,8 @@ int board_init(void)
> gd->bd->bi_arch_number = MACH_TYPE_OMAP5_SEVM;
> gd->bd->bi_boot_params = (0x80000000 + 0x100); /* boot param addr */
>
> + tca642x_set_inital_state(CONFIG_SYS_I2C_TCA642X_ADDR, tca642x_init);
> +
> return 0;
> }
>
> diff --git a/board/ti/omap5_uevm/mux_data.h b/board/ti/omap5_uevm/mux_data.h
> index a82795d..7e6415e 100644
> --- a/board/ti/omap5_uevm/mux_data.h
> +++ b/board/ti/omap5_uevm/mux_data.h
> @@ -56,6 +56,8 @@ const struct pad_conf_entry core_padconf_array_essential[] = {
> {USBD0_HS_DP, (IEN | M0)}, /* USBD0_HS_DP */
> {USBD0_HS_DM, (IEN | M0)}, /* USBD0_HS_DM */
> {USBD0_SS_RX, (IEN | M0)}, /* USBD0_SS_RX */
> + {I2C5_SCL, (IEN | M0)}, /* I2C5_SCL */
> + {I2C5_SDA, (IEN | M0)}, /* I2C5_SDA */
>
> };
>
> diff --git a/include/configs/omap5_uevm.h b/include/configs/omap5_uevm.h
> index 46dacc2..bee1278 100644
> --- a/include/configs/omap5_uevm.h
> +++ b/include/configs/omap5_uevm.h
> @@ -53,6 +53,11 @@
> #define CONFIG_PARTITION_UUIDS
> #define CONFIG_CMD_PART
>
> +#define CONFIG_TCA642X
> +#define CONFIG_CMD_TCA642X
> +#define CONFIG_SYS_I2C_TCA642X_BUS_NUM 4
> +#define CONFIG_SYS_I2C_TCA642X_ADDR 0x22
> +
> #define CONFIG_SYS_PROMPT "OMAP5432 uEVM # "
>
> #define CONSOLEDEV "ttyO2"
>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-07-08 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 20:53 [U-Boot] [PATCH 1/2] gpio: tca642x: Add the tca642x gpio expander driver Dan Murphy
2013-07-08 20:54 ` [U-Boot] [PATCH 2/2] omap5: Configure the tca6424 gpio expander Dan Murphy
2013-07-08 21:19 ` Nishanth Menon [this message]
2013-07-09 16:20 ` Dan Murphy
2013-07-08 21:27 ` [U-Boot] [PATCH 1/2] gpio: tca642x: Add the tca642x gpio expander driver Nishanth Menon
2013-07-09 16:17 ` Dan Murphy
2013-07-09 16:21 ` Nishanth Menon
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=51DB2CE6.3060808@ti.com \
--to=nm@ti.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