From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/7] ARM: OMAP5/DRA7: Expose do_set_iodelay
Date: Tue, 15 Mar 2016 18:09:16 -0500 [thread overview]
Message-ID: <1458083357-31509-7-git-send-email-nm@ti.com> (raw)
In-Reply-To: <1458083357-31509-1-git-send-email-nm@ti.com>
do_set_iodelay can now be used from board files based on needs of the
platforms variation they have.
Signed-off-by: Nishanth Menon <nm@ti.com>
---
arch/arm/cpu/armv7/omap5/dra7xx_iodelay.c | 4 ++--
arch/arm/include/asm/arch-omap5/dra7xx_iodelay.h | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/arm/cpu/armv7/omap5/dra7xx_iodelay.c b/arch/arm/cpu/armv7/omap5/dra7xx_iodelay.c
index 744950f01bd9..87987308aced 100644
--- a/arch/arm/cpu/armv7/omap5/dra7xx_iodelay.c
+++ b/arch/arm/cpu/armv7/omap5/dra7xx_iodelay.c
@@ -138,8 +138,8 @@ static u32 get_cfg_reg(u16 a_delay, u16 g_delay, u32 cpde, u32 fpde)
return reg;
}
-static int do_set_iodelay(u32 base, struct iodelay_cfg_entry const *array,
- int niodelays)
+int do_set_iodelay(u32 base, struct iodelay_cfg_entry const *array,
+ int niodelays)
{
struct iodelay_cfg_entry *iodelay = (struct iodelay_cfg_entry *)array;
u32 reg, cpde, fpde, i;
diff --git a/arch/arm/include/asm/arch-omap5/dra7xx_iodelay.h b/arch/arm/include/asm/arch-omap5/dra7xx_iodelay.h
index 0de8a800c1a2..c99700403914 100644
--- a/arch/arm/include/asm/arch-omap5/dra7xx_iodelay.h
+++ b/arch/arm/include/asm/arch-omap5/dra7xx_iodelay.h
@@ -86,4 +86,6 @@ void __recalibrate_iodelay(struct pad_conf_entry const *pad, int npads,
int __recalibrate_iodelay_start(void);
void __recalibrate_iodelay_end(int ret);
+int do_set_iodelay(u32 base, struct iodelay_cfg_entry const *array,
+ int niodelays);
#endif
--
1.7.9.5
next prev parent reply other threads:[~2016-03-15 23:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 23:09 [U-Boot] [PATCH 0/7] board: ti: DRA72: Add support for SR2.0 rev C evm Nishanth Menon
2016-03-15 23:09 ` [U-Boot] [PATCH 1/7] ARM: DRA72x: Add support for detection of SR2.0 Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-15 23:09 ` [U-Boot] [PATCH 2/7] ARM: DRA7: hwdata: Update ioreg data for DRA72 SR2.0 Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-15 23:09 ` [U-Boot] [PATCH 3/7] ARM: DRA72: sdram: Update sdram ext phy configuration for SR2.0 Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-15 23:09 ` [U-Boot] [PATCH 4/7] board: ti: DRA72: revC evm: Update sdram timing " Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-15 23:09 ` [U-Boot] [PATCH 5/7] ARM: OMAP5/DRA7: Split iodelay functionality into sub steps Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-15 23:09 ` Nishanth Menon [this message]
2016-03-16 14:24 ` [U-Boot] [PATCH 6/7] ARM: OMAP5/DRA7: Expose do_set_iodelay Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot,6/7] " Tom Rini
2016-03-15 23:09 ` [U-Boot] [PATCH 7/7] board: ti: DRA7: Add DRA72-rev C evm pinmux Nishanth Menon
2016-03-16 14:24 ` Tom Rini
2016-03-27 22:24 ` [U-Boot] [U-Boot, " Tom Rini
2016-03-16 4:09 ` [U-Boot] [PATCH 0/7] board: ti: DRA72: Add support for SR2.0 rev C evm Lokesh Vutla
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=1458083357-31509-7-git-send-email-nm@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