OMAP-GPMC: generic time calc, prepare for driver
Subsystems (7)
v7 cover OMAP-GPMC: generic time calc, prepare for driver
Hi,
This version - v7 as compared to previous version, takes care of rounding issues due to the usage of nanoseconds in generic timing routine. All calculations are now in picoseconds. Once all timings are calculated it is converted to nanoseconds so that calculated timing values are compatible with existing custom timing routines (this will help in reverting back to custom routines easily in case of any issues). And documentation has been added on gpmc timings. Also redundant rounding of nand timings has been removed as part of this series.
**********************************************************************
Abstract:
This series provides a generic gpmc timing calculation routine. There were three peripherals (OneNAND, tusb6010, smc91x) using custom timing calculations, they are migrated to use the generic timing calculation.
Such a generic routine would help create a driver out of gpmc platform code, which would be peripheral agnostic and thus lead to DT finally. Input to generic timing calculation routine would be gpmc peripheral timings, output - translated timings that gpmc can understand. Later, to DT'ify, gpmc peripheral timings could be passed through DT. Input timings that has been used here are selected such that it represents those that are present in peripheral timing datasheets.
Also this series contains minor cleanups that were low hanging fruits came across upon implementing generic timing routine. One such is credited to Jon Hunter, relevant patch is 1/2 of his series @ http://marc.info/?l=linux-omap&m=134090910321284&w=2
**********************************************************************
Proposed generic routine has been tested on OneNAND (async) on OMAP3EVM rev C (as mainline does not have the OneNAND support for this, local patch were used to test). For other cases of custom timing calculation (tusb6010, smc91x non-muxed, OneNAND sync), generic timing calculation routine was verified by simulating on OMAP3EVM.
This series is available
@ git://gitorious.org/x0148406-public/linux-kernel.git gpmc-prep-v7
and is based on
linux-next (next-20120918)Regards
Afzal
v7:
1. Use picoseconds throughout generic timing routine to prevent rounding error.
2. Documentation on gpmc timings
3. Remove redundant rounding of nand timings (a new patch)
v6:
1. Generic timing calculation, move existing users of custom calculation to use the new generic one
2. Set OneNAND part to async mode before gpmc configuration
3. Move extra delay time user handling to proper patch (3/10 -> 2/10)
4. Modify nand init for OMAP3EVM too as support got added
v5:
Use flags for sync_read/write, hv, vhf
v4:
Reorganize OneNAND set_sync/async functions in a better way
v3:
1. Refactor OneNAND set_sync/async functions to separate out timing and configurations
2. Handle bool type timings too
3. Swap patches 2 & 3 due to dependency of OneNAND change on newly added bool type timings
v2:
1. Make use of timing api for setting clock activation time, and remove direct writing to register for clock activation.
2. Move ensuring that async mode in OneNAND has been setup from set_sync to setup function, improve commit message
Afzal Mohammed (10):
ARM: OMAP2+: nand: unify init functions
ARM: OMAP2+: nand: remove redundant rounding
ARM: OMAP2+: gpmc: handle additional timings
ARM: OMAP2+: onenand: refactor for clarity
ARM: OMAP2+: gpmc: find features by ip rev check
ARM: OMAP2+: gpmc: remove cs# in sync clk div calc
ARM: OMAP2+: gpmc: generic timing calculation
ARM: OMAP2+: onenand: generic timing calculation
ARM: OMAP2+: smc91x: generic timing calculation
ARM: OMAP2+: tusb6010: generic timing calculation
Jon Hunter (1):
ARM: OMAP2+: GPMC: Remove unused OneNAND get_freq() platform function
Documentation/bus-devices/ti-gpmc.txt | 77 ++++++ arch/arm/mach-omap2/board-devkit8000.c | 8 +- arch/arm/mach-omap2/board-flash.c | 45 ++-- arch/arm/mach-omap2/board-flash.h | 6 +- arch/arm/mach-omap2/board-igep0020.c | 2 +- arch/arm/mach-omap2/board-ldp.c | 4 +- arch/arm/mach-omap2/board-omap3beagle.c | 8 +- arch/arm/mach-omap2/board-omap3evm.c | 8 +- arch/arm/mach-omap2/board-omap3touchbook.c | 8 +- arch/arm/mach-omap2/board-overo.c | 7 +- arch/arm/mach-omap2/board-zoom.c | 5 +- arch/arm/mach-omap2/common-board-devices.c | 45 ---- arch/arm/mach-omap2/common-board-devices.h | 1 - arch/arm/mach-omap2/gpmc-nand.c | 30 +-- arch/arm/mach-omap2/gpmc-onenand.c | 334 +++++++++++-------------- arch/arm/mach-omap2/gpmc-smc91x.c | 43 ++-- arch/arm/mach-omap2/gpmc.c | 383 ++++++++++++++++++++++++++++- arch/arm/mach-omap2/usb-tusb6010.c | 181 ++++---------- arch/arm/plat-omap/include/plat/gpmc.h | 114 +++++++-- arch/arm/plat-omap/include/plat/onenand.h | 8 - 20 files changed, 836 insertions(+), 481 deletions(-) create mode 100644 Documentation/bus-devices/ti-gpmc.txt
Signature · 1 line
1.7.12
PATCH v7 1/11 ARM: OMAP2+: nand: unify init functions
Helper function for updating nand platform data has been added the capability to take timing structure arguement. Usage of omap_nand_flash_init() has been replaced by modifed one, omap_nand_flash_init was doing things similar to board_nand_init except that NAND CS# were being acquired based on bootloader setting. As CS# is hardwired for a given board, acquiring gpmc CS# has been removed, and updated with the value on board.
NAND CS# used in beagle board & omap3evm was found to be CS0. Thomas Weber <[email protected]> reported that value of devkit8000 to be CS0. Overo board was found to be using CS0 based on u-boot, while google grep says omap3touchbook too has CS0.
---
v6: Modify nand init for OMAP3EVM too as support got added
arch/arm/mach-omap2/board-devkit8000.c | 8 ++++-- arch/arm/mach-omap2/board-flash.c | 45 +++++++++++++++--------------- arch/arm/mach-omap2/board-flash.h | 6 ++-- arch/arm/mach-omap2/board-igep0020.c | 2 +- arch/arm/mach-omap2/board-ldp.c | 4 +-- arch/arm/mach-omap2/board-omap3beagle.c | 8 ++++-- arch/arm/mach-omap2/board-omap3evm.c | 8 ++++-- arch/arm/mach-omap2/board-omap3touchbook.c | 8 ++++-- arch/arm/mach-omap2/board-overo.c | 7 +++-- arch/arm/mach-omap2/board-zoom.c | 5 ++-- arch/arm/mach-omap2/common-board-devices.c | 45 ------------------------------ arch/arm/mach-omap2/common-board-devices.h | 1 - 12 files changed, 62 insertions(+), 85 deletions(-)
arch/arm/mach-omap2/board-devkit8000.c +6 -2
@@ -55,8 +55,11 @@#include "sdram-micron-mt46h32m32lf-6.h" #include "mux.h" #include "hsmmc.h" +#include "board-flash.h" #include "common-board-devices.h" +#define NAND_CS 0 +#define OMAP_DM9000_GPIO_IRQ 25#define OMAP3_DEVKIT_TS_GPIO 27
@@ -621,8 +624,9 @@ static void __init devkit8000_init(void)usb_musb_init (NULL );usbhs_init (&usbhs_bdata); -omap_nand_flash_init (NAND_BUSWIDTH_16 , devkit8000_nand_partitions, -ARRAY_SIZE (devkit8000_nand_partitions)); +board_nand_init (devkit8000_nand_partitions, +ARRAY_SIZE (devkit8000_nand_partitions),NAND_CS , +NAND_BUSWIDTH_16 ,NULL );omap_twl4030_audio_init ("omap3beagle" );/* Ensure SDRC pins are mux'd for self-refresh */
arch/arm/mach-omap2/board-flash.c +23 -22
69 lines not on this page · raw message
arch/arm/mach-omap2/board-flash.h +4 -2
@@ -40,12 +40,14 @@ static inline void board_flash_init(struct flash_partitions part[],#if defined(CONFIG_MTD_NAND_OMAP2 ) || \ defined(CONFIG_MTD_NAND_OMAP2_MODULE )extern void board_nand_init (struct mtd_partition *nand_parts, -u8 nr_parts,u8 cs,int nand_type); +u8 nr_parts,u8 cs,int nand_type,struct gpmc_timings *gpmc_t); +extern struct gpmc_timings nand_default_timings[];#else static inline void board_nand_init (struct mtd_partition *nand_parts, -u8 nr_parts,u8 cs,int nand_type) +u8 nr_parts,u8 cs,int nand_type,struct gpmc_timings *gpmc_t) { } +#define nand_default_timings NULL#endif #if defined(CONFIG_MTD_ONENAND_OMAP2) || \
arch/arm/mach-omap2/board-igep0020.c +1 -1
@@ -175,7 +175,7 @@ static void __init igep_flash_init(void)pr_info ("IGEP: initializing NAND memory device\n" );board_nand_init (igep_flash_partitions,ARRAY_SIZE (igep_flash_partitions), -0 ,NAND_BUSWIDTH_16 ); +0 ,NAND_BUSWIDTH_16 , nand_default_timings); }else if (mux ==IGEP_SYSBOOT_ONENAND ) {pr_info ("IGEP: initializing OneNAND memory device\n" ); board_onenand_init(igep_flash_partitions,
arch/arm/mach-omap2/board-ldp.c +2 -2
@@ -420,8 +420,8 @@ static void __init omap_ldp_init(void)omap_serial_init ();omap_sdrc_init (NULL ,NULL );usb_musb_init (NULL ); -board_nand_init (ldp_nand_partitions, -ARRAY_SIZE (ldp_nand_partitions),ZOOM_NAND_CS ,0 ); +board_nand_init (ldp_nand_partitions,ARRAY_SIZE (ldp_nand_partitions), +ZOOM_NAND_CS ,0 , nand_default_timings);omap_hsmmc_init (mmc);ldp_display_init ();
arch/arm/mach-omap2/board-omap3beagle.c +6 -2
@@ -49,8 +49,11 @@#include "mux.h" #include "hsmmc.h" #include "pm.h" +#include "board-flash.h" #include "common-board-devices.h" +#define NAND_CS 0 +/* * OMAP3 Beagle revision * Run time detection of Beagle revision is done by reading GPIO.
@@ -512,8 +515,9 @@ static void __init omap3_beagle_init(void)usb_musb_init (NULL );usbhs_init (&usbhs_bdata); -omap_nand_flash_init (NAND_BUSWIDTH_16 , omap3beagle_nand_partitions, -ARRAY_SIZE (omap3beagle_nand_partitions)); +board_nand_init (omap3beagle_nand_partitions, +ARRAY_SIZE (omap3beagle_nand_partitions),NAND_CS , +NAND_BUSWIDTH_16 ,NULL );omap_twl4030_audio_init ("omap3beagle" );/* Ensure msecure is mux'd to be able to set the RTC. */
arch/arm/mach-omap2/board-omap3evm.c +6 -2
@@ -56,6 +56,9 @@#include "sdram-micron-mt46h32m32lf-6.h" #include "hsmmc.h" #include "common-board-devices.h" +#include "board-flash.h" + +#define NAND_CS 0#define OMAP3_EVM_TS_GPIO 175#define OMAP3_EVM_EHCI_VBUS 22
@@ -732,8 +735,9 @@ static void __init omap3_evm_init(void) }usb_musb_init (&musb_board_data);usbhs_init (&usbhs_bdata); -omap_nand_flash_init (NAND_BUSWIDTH_16 , omap3evm_nand_partitions, -ARRAY_SIZE (omap3evm_nand_partitions)); +board_nand_init (omap3evm_nand_partitions, +ARRAY_SIZE (omap3evm_nand_partitions),NAND_CS , +NAND_BUSWIDTH_16 ,NULL );omap_ads7846_init (1 ,OMAP3_EVM_TS_GPIO ,310 ,NULL );omap3evm_init_smsc911x ();
arch/arm/mach-omap2/board-omap3touchbook.c +6 -2
@@ -50,6 +50,7 @@#include "mux.h" #include "hsmmc.h" +#include "board-flash.h" #include "common-board-devices.h" #include <asm/setup.h>
@@ -59,6 +60,8 @@#define TB_BL_PWM_TIMER 9#define TB_KILL_POWER_GPIO 168 +#define NAND_CS 0 +static unsigned long touchbook_revision;static struct mtd_partition omap3touchbook_nand_partitions[] = {
@@ -365,8 +368,9 @@ static void __init omap3_touchbook_init(void)omap_ads7846_init (4 ,OMAP3_TS_GPIO ,310 , &ads7846_pdata);usb_musb_init (NULL );usbhs_init (&usbhs_bdata); -omap_nand_flash_init (NAND_BUSWIDTH_16 , omap3touchbook_nand_partitions, -ARRAY_SIZE (omap3touchbook_nand_partitions)); +board_nand_init (omap3touchbook_nand_partitions, +ARRAY_SIZE (omap3touchbook_nand_partitions),NAND_CS , +NAND_BUSWIDTH_16 ,NULL );/* Ensure SDRC pins are mux'd for self-refresh */ omap_mux_init_signal ("sdrc_cke0" ,OMAP_PIN_OUTPUT );
arch/arm/mach-omap2/board-overo.c +5 -2
@@ -54,8 +54,11 @@#include "mux.h" #include "sdram-micron-mt46h32m32lf-6.h" #include "hsmmc.h" +#include "board-flash.h" #include "common-board-devices.h" +#define NAND_CS 0 +#define OVERO_GPIO_BT_XGATE 15#define OVERO_GPIO_W2W_NRESET 16#define OVERO_GPIO_PENDOWN 114
@@ -494,8 +497,8 @@ static void __init overo_init(void)omap_serial_init ();omap_sdrc_init (mt46h32m32lf6_sdrc_params, mt46h32m32lf6_sdrc_params); -omap_nand_flash_init (0 , overo_nand_partitions, -ARRAY_SIZE (overo_nand_partitions)); +board_nand_init (overo_nand_partitions, +ARRAY_SIZE (overo_nand_partitions),NAND_CS ,0 ,NULL );usb_musb_init (NULL );usbhs_init (&usbhs_bdata);overo_spi_init ();
arch/arm/mach-omap2/board-zoom.c +3 -2
@@ -113,8 +113,9 @@ static void __init omap_zoom_init(void)usbhs_init (&usbhs_bdata); } -board_nand_init (zoom_nand_partitions,ARRAY_SIZE (zoom_nand_partitions), -ZOOM_NAND_CS ,NAND_BUSWIDTH_16 ); +board_nand_init (zoom_nand_partitions, +ARRAY_SIZE (zoom_nand_partitions),ZOOM_NAND_CS , +NAND_BUSWIDTH_16 , nand_default_timings);zoom_debugboard_init ();zoom_peripherals_init ();
arch/arm/mach-omap2/common-board-devices.c +0 -45
48 lines not on this page · raw message
arch/arm/mach-omap2/common-board-devices.h +0 -1
@@ -10,6 +10,5 @@ struct ads7846_platform_data;void omap_ads7846_init (int bus_num,int gpio_pendown,int gpio_debounce,struct ads7846_platform_data *board_pdata); -void omap_nand_flash_init (int opts,struct mtd_partition *parts,int n_parts);#endif /* __OMAP_COMMON_BOARD_DEVICES__ */
Signature · 1 line
1.7.12
PATCH v7 2/11 ARM: OMAP2+: nand: remove redundant rounding
In reply to Afzal Mohammedgpmc_cs_set_timings() calculate ticks to be programmed by rounding time in ns to next tick value. Hence remove redundant rounding of nanosecond timing.
--- arch/arm/mach-omap2/gpmc-nand.c | 30 +++++++++++++----------------- 1 file changed, 13 insertions(+), 17 deletions(-)
arch/arm/mach-omap2/gpmc-nand.c +13 -17
@@ -50,31 +50,27 @@ static int omap2_nand_gpmc_retime(struct omap_nand_platform_data *gpmc_nand_datamemset (&t,0 ,sizeof (t)); t.sync_clk = gpmc_nand_data->gpmc_t->sync_clk; - t.cs_on =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->cs_on); - t.adv_on =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->adv_on); + t.cs_on = gpmc_nand_data->gpmc_t->cs_on; + t.adv_on = gpmc_nand_data->gpmc_t->adv_on;/* Read */ - t.adv_rd_off =gpmc_round_ns_to_ticks ( - gpmc_nand_data->gpmc_t->adv_rd_off); + t.adv_rd_off = gpmc_nand_data->gpmc_t->adv_rd_off; t.oe_on = t.adv_on; - t.access =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->access); - t.oe_off =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->oe_off); - t.cs_rd_off =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->cs_rd_off); - t.rd_cycle =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->rd_cycle); + t.access = gpmc_nand_data->gpmc_t->access; + t.oe_off = gpmc_nand_data->gpmc_t->oe_off; + t.cs_rd_off = gpmc_nand_data->gpmc_t->cs_rd_off; + t.rd_cycle = gpmc_nand_data->gpmc_t->rd_cycle;/* Write */ - t.adv_wr_off =gpmc_round_ns_to_ticks ( - gpmc_nand_data->gpmc_t->adv_wr_off); + t.adv_wr_off = gpmc_nand_data->gpmc_t->adv_wr_off; t.we_on = t.oe_on;if (cpu_is_omap34xx ()) { - t.wr_data_mux_bus =gpmc_round_ns_to_ticks ( - gpmc_nand_data->gpmc_t->wr_data_mux_bus); - t.wr_access =gpmc_round_ns_to_ticks ( - gpmc_nand_data->gpmc_t->wr_access); + t.wr_data_mux_bus = gpmc_nand_data->gpmc_t->wr_data_mux_bus; + t.wr_access = gpmc_nand_data->gpmc_t->wr_access; } - t.we_off =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->we_off); - t.cs_wr_off =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->cs_wr_off); - t.wr_cycle =gpmc_round_ns_to_ticks (gpmc_nand_data->gpmc_t->wr_cycle); + t.we_off = gpmc_nand_data->gpmc_t->we_off; + t.cs_wr_off = gpmc_nand_data->gpmc_t->cs_wr_off; + t.wr_cycle = gpmc_nand_data->gpmc_t->wr_cycle;/* Configure GPMC */ if (gpmc_nand_data->devsize ==NAND_BUSWIDTH_16 )
Signature · 1 line
1.7.12
PATCH v7 3/11 ARM: OMAP2+: gpmc: handle additional timings
In reply to Afzal MohammedConfigure busturnaround, cycle2cycledelay, waitmonitoringtime, clkactivationtime in gpmc_cs_set_timings(). This is done so that boards can configure these parameters of gpmc in Kernel instead of relying on bootloader. Also configure bool type timings like extradelay.
This needed change to the existing users that were configuring clk activation time and extra delay by directly writing to registers. Thanks to Tony for making me aware of users of clk activation and being kind enough to test the modified one.
---
v6: Move extra delay time user handling to present one from 3/10
v3: Handle bool type timings too
v2: Make use of timing api for setting clock activation time,
and remove direct writing to register for clock activation
arch/arm/mach-omap2/gpmc-onenand.c | 28 +++++--------------- arch/arm/mach-omap2/gpmc.c | 48 ++++++++++++++++++++++++++++++++++ arch/arm/mach-omap2/usb-tusb6010.c | 3 ++- arch/arm/plat-omap/include/plat/gpmc.h | 19 ++++++++++++++ 4 files changed, 75 insertions(+), 23 deletions(-)
arch/arm/mach-omap2/gpmc-onenand.c +6 -22
@@ -284,27 +284,10 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, sync_read, sync_write, hf, vhf);if (div ==1 ) { - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG2 ); - reg |= (1 <<7 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG2 , reg); - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG3 ); - reg |= (1 <<7 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG3 , reg); - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG4 ); - reg |= (1 <<7 ); - reg |= (1 <<23 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG4 , reg); - }else { - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG2 ); - reg &= ~(1 <<7 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG2 , reg); - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG3 ); - reg &= ~(1 <<7 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG3 , reg); - reg =gpmc_cs_read_reg (cs,GPMC_CS_CONFIG4 ); - reg &= ~(1 <<7 ); - reg &= ~(1 <<23 ); -gpmc_cs_write_reg (cs,GPMC_CS_CONFIG4 , reg); + t.bool_timings.cs_extra_delay = true; + t.bool_timings.adv_extra_delay = true; + t.bool_timings.oe_extra_delay = true; + t.bool_timings.we_extra_delay = true; }/* Set synchronous read timings */
@@ -329,6 +312,8 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, t.rd_cycle =gpmc_ticks_to_ns (fclk_offset + (latency +1 ) * div + ticks_cez); + t.clk_activation = fclk_offset_ns; +/* Write */ if (sync_write) { t.adv_wr_off = t.adv_rd_off;
@@ -362,7 +347,6 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, (sync_read ?GPMC_CONFIG1_READTYPE_SYNC :0 ) | (sync_write ?GPMC_CONFIG1_WRITEMULTIPLE_SUPP :0 ) | (sync_write ?GPMC_CONFIG1_WRITETYPE_SYNC :0 ) | -GPMC_CONFIG1_CLKACTIVATIONTIME (fclk_offset) | GPMC_CONFIG1_PAGE_LEN(2) | (cpu_is_omap34xx() ? 0 : (GPMC_CONFIG1_WAIT_READ_MON |
arch/arm/mach-omap2/gpmc.c +48 -0
72 lines not on this page · raw message
arch/arm/mach-omap2/usb-tusb6010.c +2 -1
@@ -174,6 +174,8 @@ static int tusb_set_sync_mode(unsigned sysclk_ps, unsigned fclk_ps) tmp = t.cs_wr_off *1000 +7000 /* t_scsn_rdy_z */ ; t.wr_cycle =next_clk (t.cs_wr_off, tmp, fclk_ps); + t.clk_activation =gpmc_ticks_to_ns (1 ); +return gpmc_cs_set_timings (sync_cs, &t); }
@@ -283,7 +285,6 @@ tusb6010_setup_interface(struct musb_hdrc_platform_data *data, | GPMC_CONFIG1_READTYPE_SYNC |GPMC_CONFIG1_WRITEMULTIPLE_SUPP |GPMC_CONFIG1_WRITETYPE_SYNC - |GPMC_CONFIG1_CLKACTIVATIONTIME (1 ) |GPMC_CONFIG1_PAGE_LEN (2 ) |GPMC_CONFIG1_WAIT_READ_MON |GPMC_CONFIG1_WAIT_WRITE_MON
arch/arm/plat-omap/include/plat/gpmc.h +19 -0
@@ -96,6 +96,17 @@ enum omap_ecc { OMAP_ECC_BCH8_CODE_HW, /* 8-bit BCH ecc code */ }; +/* bool type time settings */ +struct gpmc_bool_timings { +bool cycle2cyclediffcsen; +bool cycle2cyclesamecsen; +bool we_extra_delay; +bool oe_extra_delay; +bool adv_extra_delay; +bool cs_extra_delay; +bool time_para_granularity; +}; +/* * Note that all values in this struct are in nanoseconds except sync_clk * (which is in picoseconds), while the register values are in gpmc_fck cycles.
@@ -128,9 +139,17 @@ struct gpmc_timings {u16 rd_cycle;/* Total read cycle time */ u16 wr_cycle;/* Total write cycle time */ +u16 bus_turnaround; +u16 cycle2cycle_delay; + +u16 wait_monitoring; +u16 clk_activation; +/* The following are only on OMAP3430 */ u16 wr_access;/* WRACCESSTIME */ u16 wr_data_mux_bus;/* WRDATAONADMUXBUS */ + +struct gpmc_bool_timings bool_timings; };struct gpmc_nand_regs {
Signature · 1 line
1.7.12
PATCH v7 4/11 ARM: OMAP2+: onenand: refactor for clarity
In reply to Afzal MohammedRefactor set_async_mode & set_sync_mode functions to separate out timing calculation & actual configuration (GPMC & OneNAND side).
Thanks to Jon for his suggestions.
---
v6:
1. Set OneNAND part to async mode before gpmc configuration
2. Move extra delay time user handling away from this patch (3/10 -> 2/10)
v5: Use flags for sync_read/write, hv, vhf
v4: Reorganize OneNAND set_sync/async functions in a better way
v3: Refactor OneNAND set_sync/async functions to separate out
timing and configurations
v2: Move ensuring that async mode in OneNAND has been setup from
set_sync to setup function, improve commit message
arch/arm/mach-omap2/gpmc-onenand.c | 174 +++++++++++++++++++++++-------------- 1 file changed, 109 insertions(+), 65 deletions(-)
arch/arm/mach-omap2/gpmc-onenand.c +109 -65
@@ -15,6 +15,7 @@#include <linux/platform_device.h> #include <linux/mtd/onenand_regs.h> #include <linux/io.h> +#include <linux/err.h> #include <asm/mach/flash.h>
@@ -25,6 +26,14 @@#define ONENAND_IO_SIZE SZ_128K +#define ONENAND_FLAG_SYNCREAD (1 << 0) +#define ONENAND_FLAG_SYNCWRITE (1 << 1) +#define ONENAND_FLAG_HF (1 << 2) +#define ONENAND_FLAG_VHF (1 << 3) + +static unsigned onenand_flags; +static unsigned latency; +static struct omap_onenand_platform_data *gpmc_onenand_data;static struct resource gpmc_onenand_resource = {
@@ -38,11 +47,9 @@ static struct platform_device gpmc_onenand_device = { .resource = &gpmc_onenand_resource, }; -static int omap2_onenand_set_async_mode (int cs,void __iomem *onenand_base) +static struct gpmc_timings omap2_onenand_calc_async_timings (void ) {struct gpmc_timings t; -u32 reg; -int err;const int t_cer =15 ;const int t_avdp =12 ;
@@ -55,11 +62,6 @@ static int omap2_onenand_set_async_mode(int cs, void __iomem *onenand_base)const int t_wpl =40 ;const int t_wph =30 ; -/* Ensure sync read and sync write are disabled */ - reg =readw (onenand_base +ONENAND_REG_SYS_CFG1 ); - reg &= ~ONENAND_SYS_CFG1_SYNC_READ & ~ONENAND_SYS_CFG1_SYNC_WRITE ; -writew (reg, onenand_base +ONENAND_REG_SYS_CFG1 ); -memset (&t,0 ,sizeof (t)); t.sync_clk =0 ; t.cs_on =0 ;
@@ -86,25 +88,30 @@ static int omap2_onenand_set_async_mode(int cs, void __iomem *onenand_base) t.cs_wr_off = t.we_off +gpmc_round_ns_to_ticks (t_wph); t.wr_cycle = t.cs_wr_off +gpmc_round_ns_to_ticks (t_cez); +return t; +} + +static int gpmc_set_async_mode (int cs,struct gpmc_timings *t) +{/* Configure GPMC for asynchronous read */ gpmc_cs_write_reg (cs,GPMC_CS_CONFIG1 ,GPMC_CONFIG1_DEVICESIZE_16 |GPMC_CONFIG1_MUXADDDATA ); - err =gpmc_cs_set_timings (cs, &t); -if (err) -return err; +return gpmc_cs_set_timings (cs, t); +} + +static void omap2_onenand_set_async_mode (void __iomem *onenand_base) +{ +u32 reg;/* Ensure sync read and sync write are disabled */ reg =readw (onenand_base +ONENAND_REG_SYS_CFG1 ); reg &= ~ONENAND_SYS_CFG1_SYNC_READ & ~ONENAND_SYS_CFG1_SYNC_WRITE ;writew (reg, onenand_base +ONENAND_REG_SYS_CFG1 ); - -return 0 ; } -static void set_onenand_cfg (void __iomem *onenand_base,int latency, -int sync_read,int sync_write,int hf,int vhf) +static void set_onenand_cfg (void __iomem *onenand_base) {u32 reg;
@@ -112,19 +119,19 @@ static void set_onenand_cfg(void __iomem *onenand_base, int latency, reg &= ~((0x7 <<ONENAND_SYS_CFG1_BRL_SHIFT ) | (0x7 <<9 )); reg |= (latency <<ONENAND_SYS_CFG1_BRL_SHIFT ) |ONENAND_SYS_CFG1_BL_16 ; -if (sync_read) +if (onenand_flags &ONENAND_FLAG_SYNCREAD ) reg |=ONENAND_SYS_CFG1_SYNC_READ ;else reg &= ~ONENAND_SYS_CFG1_SYNC_READ ; -if (sync_write) +if (onenand_flags &ONENAND_FLAG_SYNCWRITE ) reg |=ONENAND_SYS_CFG1_SYNC_WRITE ;else reg &= ~ONENAND_SYS_CFG1_SYNC_WRITE ; -if (hf) +if (onenand_flags &ONENAND_FLAG_HF ) reg |=ONENAND_SYS_CFG1_HF ;else reg &= ~ONENAND_SYS_CFG1_HF ; -if (vhf) +if (onenand_flags &ONENAND_FLAG_VHF ) reg |=ONENAND_SYS_CFG1_VHF ;else reg &= ~ONENAND_SYS_CFG1_VHF ;
@@ -172,9 +179,9 @@ static int omap2_onenand_get_freq(struct omap_onenand_platform_data *cfg,return freq; } -static int omap2_onenand_set_sync_mode (struct omap_onenand_platform_data *cfg, -void __iomem *onenand_base, -int *freq_ptr) +static struct gpmc_timings +omap2_onenand_calc_sync_timings (struct omap_onenand_platform_data *cfg, +int freq,bool clk_dep) {struct gpmc_timings t;const int t_cer =15 ;
@@ -184,29 +191,14 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg,const int t_wpl =40 ;const int t_wph =30 ;int min_gpmc_clk_period, t_ces, t_avds, t_avdh, t_ach, t_aavdh, t_rdyo; -int div, fclk_offset_ns, fclk_offset, gpmc_clk_ns, latency; -int first_time =0 , hf =0 , vhf =0 , sync_read =0 , sync_write =0 ; -int err, ticks_cez; -int cs = cfg->cs, freq = *freq_ptr; -u32 reg; -bool clk_dep = false; - -if (cfg->flags &ONENAND_SYNC_READ ) { - sync_read =1 ; - }else if (cfg->flags &ONENAND_SYNC_READWRITE ) { - sync_read =1 ; - sync_write =1 ; - }else -return omap2_onenand_set_async_mode (cs, onenand_base); +int div, fclk_offset_ns, fclk_offset, gpmc_clk_ns; +int ticks_cez; +int cs = cfg->cs; -if (!freq) { -/* Very first call freq is not known */ - err =omap2_onenand_set_async_mode (cs, onenand_base); -if (err) -return err; - freq =omap2_onenand_get_freq (cfg, onenand_base, &clk_dep); - first_time =1 ; - } +if (cfg->flags &ONENAND_SYNC_READ ) + onenand_flags =ONENAND_FLAG_SYNCREAD ; +else if (cfg->flags &ONENAND_SYNC_READWRITE ) + onenand_flags =ONENAND_FLAG_SYNCREAD |ONENAND_FLAG_SYNCWRITE ;switch (freq) {case 104 :
@@ -244,19 +236,23 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, t_ach =9 ; t_aavdh =7 ; t_rdyo =15 ; - sync_write =0 ; + onenand_flags &= ~ONENAND_FLAG_SYNCWRITE ;break ; } div =gpmc_cs_calc_divider (cs, min_gpmc_clk_period); gpmc_clk_ns =gpmc_ticks_to_ns (div);if (gpmc_clk_ns <15 )/* >66Mhz */ - hf =1 ; + onenand_flags |=ONENAND_FLAG_HF ; +else + onenand_flags &= ~ONENAND_FLAG_HF ;if (gpmc_clk_ns <12 )/* >83Mhz */ - vhf =1 ; -if (vhf) + onenand_flags |=ONENAND_FLAG_VHF ; +else + onenand_flags &= ~ONENAND_FLAG_VHF ; +if (onenand_flags &ONENAND_FLAG_VHF ) latency =8 ; -else if (hf) +else if (onenand_flags &ONENAND_FLAG_HF ) latency =6 ;else if (gpmc_clk_ns >=25 )/* 40 MHz*/ latency =3 ;
@@ -279,9 +275,8 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, } } -if (first_time) -set_onenand_cfg (onenand_base, latency, - sync_read, sync_write, hf, vhf); +/* Set synchronous read timings */ +memset (&t,0 ,sizeof (t));if (div ==1 ) { t.bool_timings.cs_extra_delay = true;
@@ -290,8 +285,6 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, t.bool_timings.we_extra_delay = true; } -/* Set synchronous read timings */ -memset (&t,0 ,sizeof (t)); t.sync_clk = min_gpmc_clk_period; t.cs_on =0 ; t.adv_on =0 ;
@@ -315,7 +308,7 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, t.clk_activation = fclk_offset_ns;/* Write */ -if (sync_write) { +if (onenand_flags &ONENAND_FLAG_SYNCWRITE ) { t.adv_wr_off = t.adv_rd_off; t.we_on =0 ; t.we_off = t.cs_rd_off;
@@ -340,6 +333,14 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg, } } +return t; +} + +static int gpmc_set_sync_mode (int cs,struct gpmc_timings *t) +{ +unsigned sync_read = onenand_flags &ONENAND_FLAG_SYNCREAD ; +unsigned sync_write = onenand_flags &ONENAND_FLAG_SYNCWRITE ; +/* Configure GPMC for synchronous read */ gpmc_cs_write_reg(cs, GPMC_CS_CONFIG1, GPMC_CONFIG1_WRAPBURST_SUPP |
@@ -355,11 +356,47 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg,GPMC_CONFIG1_DEVICETYPE_NOR | GPMC_CONFIG1_MUXADDDATA); - err =gpmc_cs_set_timings (cs, &t); -if (err) -return err; +return gpmc_cs_set_timings (cs, t); +} + +static int omap2_onenand_setup_async (void __iomem *onenand_base) +{ +struct gpmc_timings t; +int ret; + +omap2_onenand_set_async_mode (onenand_base); + + t =omap2_onenand_calc_async_timings (); + + ret =gpmc_set_async_mode (gpmc_onenand_data->cs, &t); +if (IS_ERR_VALUE (ret)) +return ret; + +omap2_onenand_set_async_mode (onenand_base); + +return 0 ; +} + +static int omap2_onenand_setup_sync (void __iomem *onenand_base,int *freq_ptr) +{ +int ret, freq = *freq_ptr; +struct gpmc_timings t; +bool clk_dep = false; + +if (!freq) { +/* Very first call freq is not known */ + freq =omap2_onenand_get_freq (gpmc_onenand_data, + onenand_base, &clk_dep); +set_onenand_cfg (onenand_base); + } + + t =omap2_onenand_calc_sync_timings (gpmc_onenand_data, freq, clk_dep); -set_onenand_cfg (onenand_base, latency, sync_read, sync_write, hf, vhf); + ret =gpmc_set_sync_mode (gpmc_onenand_data->cs, &t); +if (IS_ERR_VALUE (ret)) +return ret; + +set_onenand_cfg (onenand_base); *freq_ptr = freq;
@@ -369,15 +406,22 @@ static int omap2_onenand_set_sync_mode(struct omap_onenand_platform_data *cfg,static int gpmc_onenand_setup (void __iomem *onenand_base,int *freq_ptr) {struct device *dev = &gpmc_onenand_device.dev; +unsigned l =ONENAND_SYNC_READ |ONENAND_SYNC_READWRITE ; +int ret; -/* Set sync timings in GPMC */ -if (omap2_onenand_set_sync_mode (gpmc_onenand_data, onenand_base, - freq_ptr) <0 ) { -dev_err (dev,"Unable to set synchronous mode\n" ); -return -EINVAL ; + ret =omap2_onenand_setup_async (onenand_base); +if (ret) { +dev_err (dev,"unable to set to async mode\n" ); +return ret; } -return 0 ; +if (!(gpmc_onenand_data->flags & l)) +return 0 ; + + ret =omap2_onenand_setup_sync (onenand_base, freq_ptr); +if (ret) +dev_err (dev,"unable to set to sync mode\n" ); +return ret; }void __init gpmc_onenand_init (struct omap_onenand_platform_data *_onenand_data)
Signature · 1 line
1.7.12
PATCH v7 5/11 ARM: OMAP2+: GPMC: Remove unused OneNAND get_freq() platform function
In reply to Afzal MohammedFrom: Jon Hunter <[email protected]>
A platform function pointer for getting the frequency of a OneNAND device was added so that a platform could specify a custom function for returning the frequency and not just rely on the OneNAND version to determine the frequency. However, this platform function pointer is not currently being used and I am not sure if it ever has.
OneNAND devices are not so common these days and as far as I know not being used with new devices. Therefore, it is most likely that this get_freq() function pointer will not be used and so remove it.
Given that the get_freq() function pointer is not used, neither is the clk_dep variable and so all references to it can also be removed.
--- arch/arm/mach-omap2/gpmc-onenand.c | 39 ++++--------------------------- arch/arm/plat-omap/include/plat/onenand.h | 8 ------- 2 files changed, 5 insertions(+), 42 deletions(-)
arch/arm/mach-omap2/gpmc-onenand.c +5 -34
@@ -139,21 +139,10 @@ static void set_onenand_cfg(void __iomem *onenand_base) }static int omap2_onenand_get_freq (struct omap_onenand_platform_data *cfg, -void __iomem *onenand_base,bool *clk_dep) +void __iomem *onenand_base) {u16 ver =readw (onenand_base +ONENAND_REG_VERSION_ID ); -int freq =0 ; - -if (cfg->get_freq) { -struct onenand_freq_info fi; - - fi.maf_id =readw (onenand_base +ONENAND_REG_MANUFACTURER_ID ); - fi.dev_id =readw (onenand_base +ONENAND_REG_DEVICE_ID ); - fi.ver_id = ver; - freq = cfg->get_freq (&fi, clk_dep); -if (freq) -return freq; - } +int freq;switch ((ver >>4 ) &0xf ) {case 0 :
@@ -181,7 +170,7 @@ static int omap2_onenand_get_freq(struct omap_onenand_platform_data *cfg,static struct gpmc_timings omap2_onenand_calc_sync_timings (struct omap_onenand_platform_data *cfg, -int freq,bool clk_dep) +int freq) {struct gpmc_timings t;const int t_cer =15 ;
@@ -259,22 +248,6 @@ omap2_onenand_calc_sync_timings(struct omap_onenand_platform_data *cfg,else latency =4 ; -if (clk_dep) { -if (gpmc_clk_ns <12 ) {/* >83Mhz */ - t_ces =3 ; - t_avds =4 ; - }else if (gpmc_clk_ns <15 ) {/* >66Mhz */ - t_ces =5 ; - t_avds =4 ; - }else if (gpmc_clk_ns <25 ) {/* >40Mhz */ - t_ces =6 ; - t_avds =5 ; - }else { - t_ces =7 ; - t_avds =7 ; - } - } -/* Set synchronous read timings */ memset (&t,0 ,sizeof (t));
@@ -381,16 +354,14 @@ static int omap2_onenand_setup_sync(void __iomem *onenand_base, int *freq_ptr) {int ret, freq = *freq_ptr;struct gpmc_timings t; -bool clk_dep = false;if (!freq) {/* Very first call freq is not known */ - freq =omap2_onenand_get_freq (gpmc_onenand_data, - onenand_base, &clk_dep); + freq =omap2_onenand_get_freq (gpmc_onenand_data, onenand_base);set_onenand_cfg (onenand_base); } - t =omap2_onenand_calc_sync_timings (gpmc_onenand_data, freq, clk_dep); + t =omap2_onenand_calc_sync_timings (gpmc_onenand_data, freq); ret =gpmc_set_sync_mode (gpmc_onenand_data->cs, &t);if (IS_ERR_VALUE (ret))
arch/arm/plat-omap/include/plat/onenand.h +0 -8
@@ -15,20 +15,12 @@#define ONENAND_SYNC_READ (1 << 0)#define ONENAND_SYNC_READWRITE (1 << 1) -struct onenand_freq_info { -u16 maf_id; -u16 dev_id; -u16 ver_id; -}; -struct omap_onenand_platform_data {int cs;int gpio_irq;struct mtd_partition *parts;int nr_parts;int (*onenand_setup)(void __iomem *,int *freq_ptr); -int (*get_freq)(const struct onenand_freq_info *freq_info, -bool *clk_dep);int dma_channel;u8 flags;u8 regulator_can_sleep;
Signature · 1 line
1.7.12
PATCH v7 6/11 ARM: OMAP2+: gpmc: find features by ip rev check
In reply to Afzal MohammedNewer IP's have wr_access and wr_data_mux_bus fields. Use IP revision values to determine availability of these fields and hence decide on whether to configure them.
--- arch/arm/mach-omap2/gpmc.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
arch/arm/mach-omap2/gpmc.c +10 -2
@@ -90,6 +90,11 @@#define ENABLE_PREFETCH (0x1 << 7)#define DMA_MPU_MODE 2 +#define GPMC_REVISION_MAJOR (l) ((l >> 4) & 0xf) + +#define GPMC_HAS_WR_ACCESS 0x1 +#define GPMC_HAS_WR_DATA_MUX_BUS 0x2 +/* XXX: Only NAND irq has been considered,currently these are the only ones used */ #define GPMC_NR_IRQ 2
@@ -136,6 +141,7 @@ static DEFINE_SPINLOCK(gpmc_mem_lock);static unsigned int gpmc_cs_map;/* flag for cs which are initialized */ static int gpmc_ecc_used = -EINVAL ;/* cs using ecc engine */ +static unsigned gpmc_capability;static void __iomem *gpmc_base;static struct clk *gpmc_l3_clk;
@@ -364,10 +370,10 @@ int gpmc_cs_set_timings(int cs, const struct gpmc_timings *t)GPMC_SET_ONE (GPMC_CS_CONFIG1 ,18 ,19 , wait_monitoring);GPMC_SET_ONE (GPMC_CS_CONFIG1 ,25 ,26 , clk_activation); -if (cpu_is_omap34xx ()) { +if (gpmc_capability &GPMC_HAS_WR_DATA_MUX_BUS )GPMC_SET_ONE (GPMC_CS_CONFIG6 ,16 ,19 , wr_data_mux_bus); +if (gpmc_capability &GPMC_HAS_WR_ACCESS )GPMC_SET_ONE (GPMC_CS_CONFIG6 ,24 ,28 , wr_access); - }/* caller is expected to have initialized CONFIG1 to cover * at least sync vs async
@@ -930,6 +936,8 @@ static int __init gpmc_init(void)clk_enable (gpmc_l3_clk); l =gpmc_read_reg (GPMC_REVISION ); +if (GPMC_REVISION_MAJOR (l) >0x4 ) + gpmc_capability =GPMC_HAS_WR_ACCESS |GPMC_HAS_WR_DATA_MUX_BUS ;printk (KERN_INFO "GPMC revision %d.%d\n" , (l >>4 ) &0x0f , l &0x0f );/* Set smart idle mode and automatic L3 clock gating */ l =gpmc_read_reg (GPMC_SYSCONFIG );
Signature · 1 line
1.7.12
PATCH v7 7/11 ARM: OMAP2+: gpmc: remove cs# in sync clk div calc
In reply to Afzal MohammedDivider value for a certain sync clk is determined solely based on gpmc fclk. CS# does not have any role here, thus remove presence of CS# in clock divider calculation API.
--- arch/arm/mach-omap2/gpmc-onenand.c | 3 +-- arch/arm/mach-omap2/gpmc.c | 4 ++-- arch/arm/plat-omap/include/plat/gpmc.h | 2 +- 3 files changed, 4 insertions(+), 5 deletions(-)
arch/arm/mach-omap2/gpmc-onenand.c +1 -2
@@ -182,7 +182,6 @@ omap2_onenand_calc_sync_timings(struct omap_onenand_platform_data *cfg,int min_gpmc_clk_period, t_ces, t_avds, t_avdh, t_ach, t_aavdh, t_rdyo;int div, fclk_offset_ns, fclk_offset, gpmc_clk_ns;int ticks_cez; -int cs = cfg->cs;if (cfg->flags &ONENAND_SYNC_READ ) onenand_flags =ONENAND_FLAG_SYNCREAD ;
@@ -229,7 +228,7 @@ omap2_onenand_calc_sync_timings(struct omap_onenand_platform_data *cfg,break ; } - div =gpmc_cs_calc_divider (cs, min_gpmc_clk_period); + div =gpmc_calc_divider (min_gpmc_clk_period); gpmc_clk_ns =gpmc_ticks_to_ns (div);if (gpmc_clk_ns <15 )/* >66Mhz */ onenand_flags |=ONENAND_FLAG_HF ;
arch/arm/mach-omap2/gpmc.c +2 -2
@@ -321,7 +321,7 @@ static int set_gpmc_timing_reg(int cs, int reg, int st_bit, int end_bit, return -1#endif -int gpmc_cs_calc_divider (int cs,unsigned int sync_clk) +int gpmc_calc_divider (unsigned int sync_clk) {int div;u32 l;
@@ -341,7 +341,7 @@ int gpmc_cs_set_timings(int cs, const struct gpmc_timings *t)int div;u32 l; - div =gpmc_cs_calc_divider (cs, t->sync_clk); + div =gpmc_calc_divider (t->sync_clk);if (div <0 )return div;
arch/arm/plat-omap/include/plat/gpmc.h +1 -1
@@ -179,7 +179,7 @@ extern unsigned long gpmc_get_fclk_period(void);extern void gpmc_cs_write_reg (int cs,int idx,u32 val);extern u32 gpmc_cs_read_reg (int cs,int idx); -extern int gpmc_cs_calc_divider (int cs,unsigned int sync_clk); +extern int gpmc_calc_divider (unsigned int sync_clk);extern int gpmc_cs_set_timings (int cs,const struct gpmc_timings *t);extern int gpmc_cs_request (int cs,unsigned long size,unsigned long *base);extern void gpmc_cs_free (int cs);
Signature · 1 line
1.7.12
PATCH v7 8/11 ARM: OMAP2+: gpmc: generic timing calculation
In reply to Afzal MohammedPresently there are three peripherals that gets it timing by runtime calculation. Those peripherals can work with frequency scaling that affects gpmc clock. But timing calculation for them are in different ways.
Here a generic runtime calculation method is proposed. Input to this function were selected so that they represent timing variables that are present in peripheral datasheets. Motive behind this was to achieve DT bindings for the inputs as is. Even though a few of the tusb6010 timings could not be made directly related to timings normally found on peripherals, expressions used were translated to those that could be justified.
There are possibilities of improving the calculations, like calculating timing for read & write operations in a more similar way. Expressions derived here were tested for async onenand on omap3evm (as vanilla Kernel does not have omap3evm onenand support, local patch was used). Other peripherals, tusb6010, smc91x calculations were validated by simulating on omap3evm.
Regarding "we_on" for onenand async, it was found that even for muxed address/data, it need not be greater than "adv_wr_off", but rather could be derived from write setup time for peripheral from start of access time, hence would more be in line with peripheral timings. With this method it was working fine. If it is required in some cases to have "we_on" same as "wr_data_mux_bus" (i.e. greater than "adv_wr_off"), another variable could be added to indicate it. But such a requirement is not expected though.
It has been observed that "adv_rd_off" & "adv_wr_off" are currently calculated by adding an offset over "oe_on" and "we_on" respectively in the case of smc91x. But peripheral datasheet does not specify so and so "adv_rd(wr)_off" has been derived (to be specific, made ignorant of "oe_on" and "we_on") observing datasheet rather than adding an offset. Hence this generic routine is expected to work for smc91x (91C96 RX51 board). This was verified on smsc911x (9220 on OMAP3EVM) - a similar ethernet controller.
Timings are calculated in ps to prevent rounding errors and converted to ns at final stage so that these values can be directly fed to gpmc_cs_set_timings(). gpmc_cs_set_timings() would be modified to take ps once all custom timing routines are replaced by the generic routine, at the same time generic timing routine would be modified to provide timings in ps. struct gpmc_timings field types are upgraded from u16 => u32 so that it can hold ps values.
Whole of this exercise is being done to achieve driver and DT conversion. If timings could not be calculated in a peripheral agnostic way, either gpmc driver would have to be peripheral gnostic or a wrapper arrangement over gpmc driver would be required.
---
v7: 1. Use picoseconds throughout generic timing routine to prevent
rounding error.
2. Documentation on gpmc timings
Documentation/bus-devices/ti-gpmc.txt | 77 ++++++++ arch/arm/mach-omap2/gpmc.c | 319 +++++++++++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/gpmc.h | 101 ++++++++--- 3 files changed, 477 insertions(+), 20 deletions(-) create mode 100644 Documentation/bus-devices/ti-gpmc.txt
Documentation/bus-devices/ti-gpmc.txt new file +77 -0
@@ -0,0 +1,77 @@ +GPMC (General Purpose Memory Controller): +========================================= + +GPMC is an unified memory controller dedicated to interfacing external +memory devices like + * Asynchronous SRAM like memories and application specific integrated + circuit devices. + * Asynchronous, synchronous, and page mode burst NOR flash devices + NAND flash + * Pseudo-SRAM devices + +GPMC is found on Texas Instruments SoC's (OMAP based) + + +GPMC generic timing calculation: +================================ + +GPMC has certain timings that has to be programmed for proper +functioning of the peripheral, while peripheral has another set of +timings. To have peripheral work with gpmc, peripheral timings has to +be translated to the form gpmc can understand. The way it has to be +translated depends on the connected peripheral. Also there is a +dependency for certain gpmc timings on gpmc clock frequency. Hence a +generic timing routine was developed to achieve above requirements. + +Generic routine provides a generic method to calculate gpmc timings +from gpmc peripheral timings. struct gpmc_device_timings fields has to +be updated with timings from the datasheet of the peripheral that is +connected to gpmc. A few of the peripheral timings can be fed either +in time or in cycles, provision to handle this scenario has been +provided (refer struct gpmc_device_timings definition). It may so +happen that timing as specified by peripheral datasheet is not present +in timing structure, in this scenario, try to correlate peripheral +timing to the one available. If that doesn't work, try to add a new +field as required by peripheral, educate generic timing routine to +handle it, make sure that it does not break any of the existing. +Then there may be cases where peripheral datasheet doesn't mention +certain fields of struct gpmc_device_timings, zero those entries. + +Generic timing routine has been verified to work properly on +multiple onenand's and tusb6010 peripherals. + +A word of caution: generic timing routine has been developed based +on understanding of gpmc timings, peripheral timings, available +custom timing routines, a kind of reverse engineering without +most of the datasheets & hardware (to be exact none of those supported +in mainline having custom timing routine) and by simulation. + +Dependency of peripheral timings on gpmc timings: + +cs_on: t_ceasu +adv_on: t_avdasu, t_ceavd +sync_clk: clk +page_burst_access: t_bacc +clk_activation: t_ces, t_avds + +adv_rd_off: t_avdp_r, t_avdh(s*) +oe_on: t_oeasu, t_aavdh(a**), t_ach(s), cyc_aavdh_oe(s) +access: t_iaa, t_oe(a), t_ce(a), t_aa(a), cyc_iaa(s), cyc_oe(s) +rd_cycle: t_rd_cycle(a), t_cez_r, t_oez, t_ce_rdyz(s) + +adv_wr_off: t_avdp_w, t_avdh(s) +we_on, wr_data_mux_bus: t_weasu, t_aavdh, cyc_aavhd_we, t_rdyo(s) +we_off: t_wpl, cyc_wpl(s) +cs_wr_off: t_wph +wr_cycle: t_cez_w, t_wr_cycle(a), t_ce_rdyz(s) + +*s - sync only +**a - async only + +Note: Many of gpmc timings are dependent on other gpmc timings (a few +gpmc timings purely dependent on other gpmc timings, a reason that +some of the gpmc timings are missing above), and it will result in +indirect dependency of peripheral timings to gpmc timings other than +mentioned above, refer timing routine for more details. To know what +these peripheral timings correspond to, please see explanations in +struct gpmc_device_timings definition.
arch/arm/mach-omap2/gpmc.c +319 -0
331 lines not on this page · raw message
arch/arm/plat-omap/include/plat/gpmc.h +81 -20
123 lines not on this page · raw message
Signature · 1 line
1.7.12
PATCH v7 8/11 ARM: OMAP2+: gpmc: generic timing calculation
Hi Afzal,
Quoted 117 lines · Afzal Mohammed
Presently there are three peripherals that gets it timing by runtime calculation. Those peripherals can work with frequency scaling that affects gpmc clock. But timing calculation for them are in different ways.
Here a generic runtime calculation method is proposed. Input to this function were selected so that they represent timing variables that are present in peripheral datasheets. Motive behind this was to achieve DT bindings for the inputs as is. Even though a few of the tusb6010 timings could not be made directly related to timings normally found on peripherals, expressions used were translated to those that could be justified.
There are possibilities of improving the calculations, like calculating timing for read & write operations in a more similar way. Expressions derived here were tested for async onenand on omap3evm (as vanilla Kernel does not have omap3evm onenand support, local patch was used). Other peripherals, tusb6010, smc91x calculations were validated by simulating on omap3evm.
Regarding "
we_on" for onenand async, it was found that even for muxed address/data, it need not be greater than "adv_wr_off", but rather could be derived from write setup time for peripheral from start of access time, hence would more be in line with peripheral timings. With this method it was working fine. If it is required in some cases to have "we_on" same as "wr_data_mux_bus" (i.e. greater than "adv_wr_off"), another variable could be added to indicate it. But such a requirement is not expected though.It has been observed that "
adv_rd_off" & "adv_wr_off" are currently calculated by adding an offset over "oe_on" and "we_on" respectively in the case of smc91x. But peripheral datasheet does not specify so and so "adv_rd(wr)_off" has been derived (to be specific, made ignorant of "oe_on" and "we_on") observing datasheet rather than adding an offset. Hence this generic routine is expected to work for smc91x (91C96 RX51 board). This was verified on smsc911x (9220 on OMAP3EVM) - a similar ethernet controller.Timings are calculated in ps to prevent rounding errors and converted to ns at final stage so that these values can be directly fed to
gpmc_cs_set_timings().gpmc_cs_set_timings()would be modified to take ps once all custom timing routines are replaced by the generic routine, at the same time generic timing routine would be modified to provide timings in ps. structgpmc_timingsfield types are upgraded from u16 => u32 so that it can hold ps values.Whole of this exercise is being done to achieve driver and DT conversion. If timings could not be calculated in a peripheral agnostic way, either gpmc driver would have to be peripheral gnostic or a wrapper arrangement over gpmc driver would be required.
Signed-off-by Afzal Mohammed <[email protected]>---
v7: 1. Use picoseconds throughout generic timing routine to prevent
rounding error.
2. Documentation on gpmc timingsDocumentation/bus-devices/ti-gpmc.txt | 77 ++++++++ arch/arm/mach-omap2/gpmc.c | 319 +++++++++++++++++++++++++++++++++ arch/arm/plat-omap/include/plat/gpmc.h | 101 ++++++++--- 3 files changed, 477 insertions(+), 20 deletions(-) create mode 100644 Documentation/bus-devices/ti-gpmc.txtDocumentation/bus-devices/ti-gpmc.txt new file +41
-0@@ -0,0 +1,77 @@ +GPMC (General Purpose Memory Controller): +========================================= + +GPMC is an unified memory controller dedicated to interfacing external +memory devices like + * Asynchronous SRAM like memories and application specific integrated + circuit devices. + * Asynchronous, synchronous, and page mode burst NOR flash devices + NAND flash + * Pseudo-SRAM devices + +GPMC is found on Texas Instruments SoC's (OMAP based) + + +GPMC generic timing calculation: +================================ + +GPMC has certain timings that has to be programmed for proper +functioning of the peripheral, while peripheral has another set of +timings. To have peripheral work with gpmc, peripheral timings has to +be translated to the form gpmc can understand. The way it has to be +translated depends on the connected peripheral. Also there is a +dependency for certain gpmc timings on gpmc clock frequency. Hence a +generic timing routine was developed to achieve above requirements. + +Generic routine provides a generic method to calculate gpmc timings +from gpmc peripheral timings. struct gpmc_device_timings fields has to +be updated with timings from the datasheet of the peripheral that is +connected to gpmc. A few of the peripheral timings can be fed either +in time or in cycles, provision to handle this scenario has been +provided (refer struct gpmc_device_timings definition). It may so +happen that timing as specified by peripheral datasheet is not present +in timing structure, in this scenario, try to correlate peripheral +timing to the one available. If that doesn't work, try to add a new +field as required by peripheral, educate generic timing routine to +handle it, make sure that it does not break any of the existing. +Then there may be cases where peripheral datasheet doesn't mention +certain fields of struct gpmc_device_timings, zero those entries. + +Generic timing routine has been verified to work properly on +multiple onenand's and tusb6010 peripherals.
Documentation/bus-devices/ti-gpmc.txt line 51
Quoted 10 lines
Documentation/bus-devices/ti-gpmc.txt new file +10
-0+ +A word of caution: generic timing routine has been developed based +on understanding of gpmc timings, peripheral timings, available +custom timing routines, a kind of reverse engineering without +most of the datasheets & hardware (to be exact none of those supported +in mainline having custom timing routine) and by simulation. + +Dependency of peripheral timings on gpmc timings: + +cs_on: t_ceasu
Thanks for adding these details. Could be good to clarify that the left-hand side parameters are the gpmc register fields and the right-hand side are the timing parameters these are calculated using.
Also, given that this is in documentation for completeness it could be good to somewhere state what "t_ceasu" means. For the gpmc register field description may be we could give a reference to an OMAP document.
Documentation/bus-devices/ti-gpmc.txt line 58
Quoted 7 lines
Documentation/bus-devices/ti-gpmc.txt new file +7
-0+adv_on: t_avdasu, t_ceavd +sync_clk: clk +page_burst_access: t_bacc +clk_activation: t_ces, t_avds + +adv_rd_off: t_avdp_r, t_avdh(s*) +oe_on: t_oeasu, t_aavdh(a**), t_ach(s), cyc_aavdh_oe(s)
Would it be better to have ...
oe_on (sync): t_oeasu, t_ach(*), cyc_aavdh_oeoe_on (async): t_oeasu, t_aavdh(*)
* - optional
I assume that the hold times from the clock (t_ach and t_aavdh) are used for fine tuning if the peripheral requires this, but a user adding a new device would not be required to specify these, where as t_oeasu is mandatory.
Or maybe should the timings be grouped as ...
General
Read Async
Read Async Address/Data Multiplexed
Read Sync
Read Sync Address/Data Multiplexed
Write Async
Write Async Address/Data Multiplexed
Write Sync
Write Sync Address/Data Multiplexed
There may be some duplication but it will be clear where things like ADV timing applies.
Quoted 48 lines
Documentation/bus-devices/ti-gpmc.txt new file +19
-0+access: t_iaa, t_oe(a), t_ce(a), t_aa(a), cyc_iaa(s), cyc_oe(s) +rd_cycle: t_rd_cycle(a), t_cez_r, t_oez, t_ce_rdyz(s) + +adv_wr_off: t_avdp_w, t_avdh(s) +we_on, wr_data_mux_bus: t_weasu, t_aavdh, cyc_aavhd_we, t_rdyo(s) +we_off: t_wpl, cyc_wpl(s) +cs_wr_off: t_wph +wr_cycle: t_cez_w, t_wr_cycle(a), t_ce_rdyz(s) + +*s - sync only +**a - async only + +Note: Many of gpmc timings are dependent on other gpmc timings (a few +gpmc timings purely dependent on other gpmc timings, a reason that +some of the gpmc timings are missing above), and it will result in +indirect dependency of peripheral timings to gpmc timings other than +mentioned above, refer timing routine for more details. To know what +these peripheral timings correspond to, please see explanations in +struct gpmc_device_timings definition.arch/arm/mach-omap2/gpmc.c +14
-0@@ -238,6 +238,18 @@ unsigned int gpmc_round_ns_to_ticks(unsigned int time_ns)return ticks *gpmc_get_fclk_period () /1000 ; } +static unsigned int gpmc_ticks_to_ps (unsigned int ticks) +{ +return ticks *gpmc_get_fclk_period (); +} + +static unsigned int gpmc_round_ps_to_ticks (unsigned int time_ps) +{ +unsigned long ticks =gpmc_ps_to_ticks (time_ps); + +return ticks *gpmc_get_fclk_period (); +} +static inline void gpmc_cs_modify_reg (int cs,int reg,u32 mask,bool value) {u32 l;@@ -892,6 +904,313 @@ static void __init gpmc_mem_init(void) } } +static u32 gpmc_round_ps_to_sync_clk (u32 time_ps,u32 sync_clk) +{
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 918
Quoted 10 lines
arch/arm/mach-omap2/gpmc.c +10
-0+u32 temp; +int div; + + div =gpmc_calc_divider (sync_clk); + temp =gpmc_ps_to_ticks (time_ps); + temp = (temp + div -1 ) / div; +return gpmc_ticks_to_ps (temp * div); +} + +/* can the cycles be avoided ? */
Nit should this be marked with a TODO?
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 927
Quoted 9 lines
arch/arm/mach-omap2/gpmc.c +9
-0+static int gpmc_calc_sync_read_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +bool mux = dev_t->mux; +u32 temp; + +/* adv_rd_off */ + temp = dev_t->t_avdp_r; +/* mux check required ? */
Nit should this be marked with a TODO?
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 936
Quoted 9 lines
arch/arm/mach-omap2/gpmc.c +9
-0+if (mux) { +/* t_avdp not to be required for sync, only added for tusb this +* indirectly necessitates requirement of t_avdp_r & t_avdp_w +* instead of having a single t_avdp +*/ + temp =max_t (u32, temp, gpmc_t->clk_activation + dev_t->t_avdh); + temp =max_t (u32, gpmc_t->adv_on +gpmc_ticks_to_ps (1 ), temp); + } + gpmc_t->adv_rd_off =gpmc_round_ps_to_ticks (temp);
Any reason why we can't return ns in the above function? Or make this function gpmc_round_ps_to_ns()? Then we could avoid having gpmc_convert_ps_to_ns() below.
Quoted 263 lines
arch/arm/mach-omap2/gpmc.c +263
-0+ +/* oe_on */ + temp = dev_t->t_oeasu;/* remove this ? */ +if (mux) { + temp =max_t (u32, temp, gpmc_t->clk_activation + dev_t->t_ach); + temp =max_t (u32, temp, gpmc_t->adv_rd_off + +gpmc_ticks_to_ps (dev_t->cyc_aavdh_oe)); + } + gpmc_t->oe_on =gpmc_round_ps_to_ticks (temp); + +/* access */ +/* any scope for improvement ?, by combining oe_on & clk_activation, +* need to check whether access = clk_activation + round to sync clk ? +*/ + temp =max_t (u32, dev_t->t_iaa, dev_t->cyc_iaa * gpmc_t->sync_clk); + temp += gpmc_t->clk_activation; +if (dev_t->cyc_oe) + temp =max_t (u32, temp, gpmc_t->oe_on + +gpmc_ticks_to_ps (dev_t->cyc_oe)); + gpmc_t->access =gpmc_round_ps_to_ticks (temp); + + gpmc_t->oe_off = gpmc_t->access +gpmc_ticks_to_ps (1 ); + gpmc_t->cs_rd_off = gpmc_t->oe_off; + +/* rd_cycle */ + temp =max_t (u32, dev_t->t_cez_r, dev_t->t_oez); + temp =gpmc_round_ps_to_sync_clk (temp, gpmc_t->sync_clk) + + gpmc_t->access; +/* barter t_ce_rdyz with t_cez_r ? */ +if (dev_t->t_ce_rdyz) + temp =max_t (u32, temp, gpmc_t->cs_rd_off + dev_t->t_ce_rdyz); + gpmc_t->rd_cycle =gpmc_round_ps_to_ticks (temp); + +return 0 ; +} + +static int gpmc_calc_sync_write_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +bool mux = dev_t->mux; +u32 temp; + +/* adv_wr_off */ + temp = dev_t->t_avdp_w; +if (mux) { + temp =max_t (u32, temp, + gpmc_t->clk_activation + dev_t->t_avdh); + temp =max_t (u32, gpmc_t->adv_on +gpmc_ticks_to_ps (1 ), temp); + } + gpmc_t->adv_wr_off =gpmc_round_ps_to_ticks (temp); + +/* wr_data_mux_bus */ + temp =max_t (u32, dev_t->t_weasu, + gpmc_t->clk_activation + dev_t->t_rdyo); +/* shouldn't mux be kept as a whole for wr_data_mux_bus ?, +* and in that case remember to handle we_on properly +*/ +if (mux) { + temp =max_t (u32, temp, + gpmc_t->adv_wr_off + dev_t->t_aavdh); + temp =max_t (u32, temp, gpmc_t->adv_wr_off + +gpmc_ticks_to_ps (dev_t->cyc_aavdh_we)); + } + gpmc_t->wr_data_mux_bus =gpmc_round_ps_to_ticks (temp); + +/* we_on */ +if (gpmc_capability &GPMC_HAS_WR_DATA_MUX_BUS ) + gpmc_t->we_on =gpmc_round_ps_to_ticks (dev_t->t_weasu); +else + gpmc_t->we_on = gpmc_t->wr_data_mux_bus; + +/* wr_access */ +/* gpmc_capability check reqd ? , even if not, will not harm */ + gpmc_t->wr_access = gpmc_t->access; + +/* we_off */ + temp = gpmc_t->we_on + dev_t->t_wpl; + temp =max_t (u32, temp, + gpmc_t->wr_access +gpmc_ticks_to_ps (1 )); + temp =max_t (u32, temp, + gpmc_t->we_on +gpmc_ticks_to_ps (dev_t->cyc_wpl)); + gpmc_t->we_off =gpmc_round_ps_to_ticks (temp); + + gpmc_t->cs_wr_off =gpmc_round_ps_to_ticks (gpmc_t->we_off + + dev_t->t_wph); + +/* wr_cycle */ + temp =gpmc_round_ps_to_sync_clk (dev_t->t_cez_w, gpmc_t->sync_clk); + temp += gpmc_t->wr_access; +/* barter t_ce_rdyz with t_cez_w ? */ +if (dev_t->t_ce_rdyz) + temp =max_t (u32, temp, + gpmc_t->cs_wr_off + dev_t->t_ce_rdyz); + gpmc_t->wr_cycle =gpmc_round_ps_to_ticks (temp); + +return 0 ; +} + +static int gpmc_calc_async_read_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +bool mux = dev_t->mux; +u32 temp; + +/* adv_rd_off */ + temp = dev_t->t_avdp_r; +if (mux) + temp =max_t (u32, gpmc_t->adv_on +gpmc_ticks_to_ps (1 ), temp); + gpmc_t->adv_rd_off =gpmc_round_ps_to_ticks (temp); + +/* oe_on */ + temp = dev_t->t_oeasu; +if (mux) + temp =max_t (u32, temp, + gpmc_t->adv_rd_off + dev_t->t_aavdh); + gpmc_t->oe_on =gpmc_round_ps_to_ticks (temp); + +/* access */ + temp =max_t (u32, dev_t->t_iaa,/* remove t_iaa in async ? */ + gpmc_t->oe_on + dev_t->t_oe); + temp =max_t (u32, temp, + gpmc_t->cs_on + dev_t->t_ce); + temp =max_t (u32, temp, + gpmc_t->adv_on + dev_t->t_aa); + gpmc_t->access =gpmc_round_ps_to_ticks (temp); + + gpmc_t->oe_off = gpmc_t->access +gpmc_ticks_to_ps (1 ); + gpmc_t->cs_rd_off = gpmc_t->oe_off; + +/* rd_cycle */ + temp =max_t (u32, dev_t->t_rd_cycle, + gpmc_t->cs_rd_off + dev_t->t_cez_r); + temp =max_t (u32, temp, gpmc_t->oe_off + dev_t->t_oez); + gpmc_t->rd_cycle =gpmc_round_ps_to_ticks (temp); + +return 0 ; +} + +static int gpmc_calc_async_write_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +bool mux = dev_t->mux; +u32 temp; + +/* adv_wr_off */ + temp = dev_t->t_avdp_w; +if (mux) + temp =max_t (u32, gpmc_t->adv_on +gpmc_ticks_to_ps (1 ), temp); + gpmc_t->adv_wr_off =gpmc_round_ps_to_ticks (temp); + +/* wr_data_mux_bus */ + temp = dev_t->t_weasu; +if (mux) { + temp =max_t (u32, temp, gpmc_t->adv_wr_off + dev_t->t_aavdh); + temp =max_t (u32, temp, gpmc_t->adv_wr_off + +gpmc_ticks_to_ps (dev_t->cyc_aavdh_we)); + } + gpmc_t->wr_data_mux_bus =gpmc_round_ps_to_ticks (temp); + +/* we_on */ +if (gpmc_capability &GPMC_HAS_WR_DATA_MUX_BUS ) + gpmc_t->we_on =gpmc_round_ps_to_ticks (dev_t->t_weasu); +else + gpmc_t->we_on = gpmc_t->wr_data_mux_bus; + +/* we_off */ + temp = gpmc_t->we_on + dev_t->t_wpl; + gpmc_t->we_off =gpmc_round_ps_to_ticks (temp); + + gpmc_t->cs_wr_off =gpmc_round_ps_to_ticks (gpmc_t->we_off + + dev_t->t_wph); + +/* wr_cycle */ + temp =max_t (u32, dev_t->t_wr_cycle, + gpmc_t->cs_wr_off + dev_t->t_cez_w); + gpmc_t->wr_cycle =gpmc_round_ps_to_ticks (temp); + +return 0 ; +} + +static int gpmc_calc_sync_common_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +u32 temp; + + gpmc_t->sync_clk =gpmc_calc_divider (dev_t->clk) * +gpmc_get_fclk_period (); + + gpmc_t->page_burst_access =gpmc_round_ps_to_sync_clk ( + dev_t->t_bacc, + gpmc_t->sync_clk); + + temp =max_t (u32, dev_t->t_ces, dev_t->t_avds); + gpmc_t->clk_activation =gpmc_round_ps_to_ticks (temp); + +if (gpmc_calc_divider (gpmc_t->sync_clk) !=1 ) +return 0 ; + +if (dev_t->ce_xdelay) + gpmc_t->bool_timings.cs_extra_delay = true; +if (dev_t->avd_xdelay) + gpmc_t->bool_timings.adv_extra_delay = true; +if (dev_t->oe_xdelay) + gpmc_t->bool_timings.oe_extra_delay = true; +if (dev_t->we_xdelay) + gpmc_t->bool_timings.we_extra_delay = true; + +return 0 ; +} + +static int gpmc_calc_common_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +u32 temp; + +/* cs_on */ + gpmc_t->cs_on =gpmc_round_ps_to_ticks (dev_t->t_ceasu); + +/* adv_on */ + temp = dev_t->t_avdasu; +if (dev_t->t_ce_avd) + temp =max_t (u32, temp, + gpmc_t->cs_on + dev_t->t_ce_avd); + gpmc_t->adv_on =gpmc_round_ps_to_ticks (temp); + +if (dev_t->sync_write || dev_t->sync_read) +gpmc_calc_sync_common_timings (gpmc_t, dev_t); + +return 0 ; +} + +static void gpmc_convert_ps_to_ns (struct gpmc_timings *t) +{ + t->cs_on /=1000 ; + t->cs_rd_off /=1000 ; + t->cs_wr_off /=1000 ; + t->adv_on /=1000 ; + t->adv_rd_off /=1000 ; + t->adv_wr_off /=1000 ; + t->we_on /=1000 ; + t->we_off /=1000 ; + t->oe_on /=1000 ; + t->oe_off /=1000 ; + t->page_burst_access /=1000 ; + t->access /=1000 ; + t->rd_cycle /=1000 ; + t->wr_cycle /=1000 ; + t->bus_turnaround /=1000 ; + t->cycle2cycle_delay /=1000 ; + t->wait_monitoring /=1000 ; + t->clk_activation /=1000 ; + t->wr_access /=1000 ; + t->wr_data_mux_bus /=1000 ; +} + +int gpmc_calc_timings (struct gpmc_timings *gpmc_t, +struct gpmc_device_timings *dev_t) +{ +memset (gpmc_t,0 ,sizeof (*gpmc_t)); + +gpmc_calc_common_timings (gpmc_t, dev_t); + +if (dev_t->sync_read)
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 1209
Quoted 10 lines
arch/arm/mach-omap2/gpmc.c +10
-0+gpmc_calc_sync_read_timings (gpmc_t, dev_t); + else +gpmc_calc_async_read_timings (gpmc_t ,dev_t ); + +if (dev_t->sync_write) +gpmc_calc_sync_write_timings (gpmc_t, dev_t); +else +gpmc_calc_async_write_timings (gpmc_t, dev_t); + +gpmc_convert_ps_to_ns (gpmc_t);
I am wondering if we could avoid this above function and then ...
Quoted 57 lines
arch/arm/mach-omap2/gpmc.c +4
-0+ +return 0 ; +} +static int __init gpmc_init (void ) {u32 l;arch/arm/plat-omap/include/plat/gpmc.h +16
-16@@ -116,42 +116,103 @@ struct gpmc_timings {u32 sync_clk;/* Chip-select signal timings corresponding to GPMC_CS_CONFIG2 */ -u16 cs_on;/* Assertion time */ -u16 cs_rd_off;/* Read deassertion time */ -u16 cs_wr_off;/* Write deassertion time */ +u32 cs_on;/* Assertion time */ +u32 cs_rd_off;/* Read deassertion time */ +u32 cs_wr_off;/* Write deassertion time */ /* ADV signal timings corresponding to GPMC_CONFIG3 */ -u16 adv_on;/* Assertion time */ -u16 adv_rd_off;/* Read deassertion time */ -u16 adv_wr_off;/* Write deassertion time */ +u32 adv_on;/* Assertion time */ +u32 adv_rd_off;/* Read deassertion time */ +u32 adv_wr_off;/* Write deassertion time */ /* WE signals timings corresponding to GPMC_CONFIG4 */ -u16 we_on;/* WE assertion time */ -u16 we_off;/* WE deassertion time */ +u32 we_on;/* WE assertion time */ +u32 we_off;/* WE deassertion time */ /* OE signals timings corresponding to GPMC_CONFIG4 */ -u16 oe_on;/* OE assertion time */ -u16 oe_off;/* OE deassertion time */ +u32 oe_on;/* OE assertion time */ +u32 oe_off;/* OE deassertion time */ /* Access time and cycle time timings corresponding to GPMC_CONFIG5 */ -u16 page_burst_access;/* Multiple access word delay */ -u16 access;/* Start-cycle to first data valid delay */ -u16 rd_cycle;/* Total read cycle time */ -u16 wr_cycle;/* Total write cycle time */ +u32 page_burst_access;/* Multiple access word delay */ +u32 access;/* Start-cycle to first data valid delay */ +u32 rd_cycle;/* Total read cycle time */ +u32 wr_cycle;/* Total write cycle time */ -u16 bus_turnaround; -u16 cycle2cycle_delay; +u32 bus_turnaround; +u32 cycle2cycle_delay;
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 150
Quoted 10 lines
arch/arm/plat-omap/include/plat/gpmc.h +4
-4-u16 wait_monitoring; -u16 clk_activation; + u32 wait_monitoring;.abctuw + u32 clk_activation;/* The following are only on OMAP3430 */ -u16 wr_access;/* WRACCESSTIME */ -u16 wr_data_mux_bus;/* WRDATAONADMUXBUS */ +u32 wr_access;/* WRACCESSTIME */ +u32 wr_data_mux_bus;/* WRDATAONADMUXBUS */
... we could keep the above u16.
Quoted 41 lines
arch/arm/plat-omap/include/plat/gpmc.h +37
-0struct gpmc_bool_timings bool_timings; }; +/* Device timings in picoseconds */ +struct gpmc_device_timings { +u32 t_ceasu;/* address setup to CS valid */ +u32 t_avdasu;/* address setup to ADV valid */ +/* XXX: try to combine t_avdp_r & t_avdp_w. Issue is +* of tusb using these timings even for sync whilst +* ideally for adv_rd/(wr)_off it should have considered +* t_avdh instead. This indirectly necessitates r/w +* variations of t_avdp as it is possible to have one +* sync & other async +*/ +u32 t_avdp_r;/* ADV low time (what about t_cer ?) */ +u32 t_avdp_w; +u32 t_aavdh;/* address hold time */ +u32 t_oeasu;/* address setup to OE valid */ +u32 t_aa;/* access time from ADV assertion */ +u32 t_iaa;/* initial access time */ +u32 t_oe;/* access time from OE assertion */ +u32 t_ce;/* access time from CS asertion */ +u32 t_rd_cycle;/* read cycle time */ +u32 t_cez_r;/* read CS deassertion to high Z */ +u32 t_cez_w;/* write CS deassertion to high Z */ +u32 t_oez;/* OE deassertion to high Z */ +u32 t_weasu;/* address setup to WE valid */ +u32 t_wpl;/* write assertion time */ +u32 t_wph;/* write deassertion time */ +u32 t_wr_cycle;/* write cycle time */ + +u32 clk; +u32 t_bacc;/* burst access valid clock to output delay */ +u32 t_ces;/* CS setup time to clk */ +u32 t_avds;/* ADV setup time to clk */ +u32 t_avdh;/* ADV hold time from clk */ +u32 t_ach;/* address hold time from clk */ +u32 t_rdyo;/* clk to ready valid */ + +u32 t_ce_rdyz;/* XXX: description ?, or use t_cez instead */
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 201
Quoted 10 lines
arch/arm/plat-omap/include/plat/gpmc.h +10
-0+u32 t_ce_avd;/* CS on to ADV on delay */ + +/* XXX: check the possibility of combining +* cyc_aavhd_oe & cyc_aavdh_we +*/ +u8 cyc_aavdh_oe; +u8 cyc_aavdh_we; +u8 cyc_oe; +u8 cyc_wpl; +u32 cyc_iaa;
May be I should look at an example, but it would be good to document what these cyc_xxx parameters are/represent.
Cheers
Jon
PATCH v7 8/11 ARM: OMAP2+: gpmc: generic timing calculation
Hi Jon,
Quoted 9 lines · Jon
Documentation/bus-devices/ti-gpmc.txt line 51
Quoted 3 lines · Afzal Mohammed
Documentation/bus-devices/ti-gpmc.txt new file +3
-0+Dependency of peripheral timings on gpmc timings: + +cs_on: t_ceasuThanks for adding these details. Could be good to clarify that the left-hand side parameters are the gpmc register fields and the right-hand side are the timing parameters these are calculated using.
Ok
Quoted 4 lines
Also, given that this is in documentation for completeness it could be good to somewhere state what "
t_ceasu" means. For the gpmc register field description may be we could give a reference to an OMAP document.
Yes, it has been mentioned, as quoted below, reason it has not been mentioned here is to avoid duplication. I will add TRM reference.
"
Quoted 8 lines
Documentation/bus-devices/ti-gpmc.txt
Quoted 8 lines
Documentation/bus-devices/ti-gpmc.txt new file +6
-0+Note: Many of gpmc timings are dependent on other gpmc timings (a few +mentioned above, refer timing routine for more details. To know what +these peripheral timings correspond to, please see explanations in +struct gpmc_device_timings definition. +struct gpmc_device_timings { + u32 t_ceasu; /* address setup to CS valid */
"
Quoted 7 lines
Documentation/bus-devices/ti-gpmc.txt line 58
Quoted 2 lines
Documentation/bus-devices/ti-gpmc.txt new file +2
-0+adv_rd_off: t_avdp_r, t_avdh(s*) +oe_on: t_oeasu, t_aavdh(a**), t_ach(s), cyc_aavdh_oe(s)Would it be better to have ...
oe_on(sync):t_oeasu,t_ach(*),cyc_aavdh_oeoe_on(async):t_oeasu,t_aavdh(*)
Ok
Quoted 6 lines
* - optional
I assume that the hold times from the clock (
t_achandt_aavdh) are used for fine tuning if the peripheral requires this, but a user adding a new device would not be required to specify these, where ast_oeasuis mandatory.
It depends on the peripheral, t_oeasu in not used for OneNAND, tusb sync, so I prefer not mentioning any timing as optional or mandatory.
Quoted 12 lines
Or maybe should the timings be grouped as ...
General
Read Async
Read Async Address/Data Multiplexed
Read Sync
Read Sync Address/Data Multiplexed
Write Async
Write Async Address/Data Multiplexed
Write Sync
Write Sync Address/Data Multiplexed
Quoted 2 lines
There may be some duplication but it will be clear where things like ADV timing applies.
I would prefer to keep it concise, but no strong opinion on it, if you prefer as above, I will change it.
Quoted 7 lines
Quoted 1 line
+/* can the cycles be avoided ? */
Nit should this be marked with a TODO?
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 927
Quoted 1 line
arch/arm/mach-omap2/gpmc.c +1
-0+/* mux check required ? */ Nit should this be marked with a TODO?
Marking XXX should Ok, right ?, reason is that they are not kept as TODO, but rather as pointers to may be possible improvements
Quoted 5 lines
Review
Quoted 1 line
(quoted diff) +1
-0+ gpmc_t->adv_rd_off = gpmc_round_ps_to_ticks(temp);Any reason why we can't return ns in the above function? Or make this function
gpmc_round_ps_to_ns()? Then we could avoid havinggpmc_convert_ps_to_ns()below.
Calculation in ps is required to get more accurate results.
Calculating in ns was the reason for issue faced on N800 for Tony with previous version.
I will explain what would have happened with v6 on N800, i.e. using ns values,
Based on logs from Tony, gpmc clk was 9ns, actually it would have been somewhere around 9115ps.
Take below timings of previous version in tusb async case
gpmc_t->oe_on = gpmc_round_ps_to_ticks(temp) / 1000;
/* access */
temp = max_t(u32, dev_t->t_iaa, /* remove t_iaa in async ? */
gpmc_t->oe_on * 1000 + dev_t->t_oe);
temp = max_t(u32, temp,
gpmc_t->cs_on * 1000 + dev_t->t_ce);
temp = max_t(u32, temp,
gpmc_t->adv_on * 1000 + dev_t->t_aa);
gpmc_t->access = gpmc_round_ps_to_ticks(temp) / 1000;Upon calculating we get,
oe_on = 63805 / 1000 = 63
and for access (t_oe = 300, t_ce = t_aa = t_iaa = 0),
temp = 63 * 1000 + 300 = 63300
access = 63300 / 1000 = 63
Here we get oe_on as well as access as 7 ticks, but access should have been 8 ticks, which is what we will get by using ps values, i.e. as in this version, as below,
gpmc_t->oe_on = gpmc_round_ps_to_ticks(temp);
/* access */
temp = max_t(u32, dev_t->t_iaa, /* remove t_iaa in async ? */
gpmc_t->oe_on + dev_t->t_oe);
temp = max_t(u32, temp,
gpmc_t->cs_on + dev_t->t_ce);
temp = max_t(u32, temp,
gpmc_t->adv_on + dev_t->t_aa);
gpmc_t->access = gpmc_round_ps_to_ticks(temp);I believe it is always better to go with higher resolution.
Quoted 3 lines
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 1209
Quoted 1 line
arch/arm/mach-omap2/gpmc.c +1
-0+gpmc_convert_ps_to_ns (gpmc_t);I am wondering if we could avoid this above function and then ...
This will be removed once it is confirmed that all the peripherals using custom runtime calculation can work with this generic routine. Then all calculation would be purely in ps.
Right now converting ps to ns has been kept only to be compatible with custom routines and so that we can easily go back to custom routines in case of any issues, quoting relevant commit message below,
"
Timings are calculated in ps to prevent rounding errors and converted to ns at final stage so that these values can be directly fed to gpmc_cs_set_timings(). gpmc_cs_set_timings() would be modified to take ps once all custom timing routines are replaced by the generic routine, at the same time generic timing routine would be modified to provide timings in ps. struct gpmc_timings field types are upgraded from u16 => u32 so that it can hold ps values.
"
Quoted 8 lines
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 118
Quoted 6 lines
arch/arm/plat-omap/include/plat/gpmc.h +2
-2@@ -116,42 +116,103 @@ struct gpmc_timings { -u16 wr_access;/* WRACCESSTIME */ -u16 wr_data_mux_bus;/* WRDATAONADMUXBUS */ +u32 wr_access;/* WRACCESSTIME */ +u32 wr_data_mux_bus;/* WRDATAONADMUXBUS */ ... we could keep the above u16.
Due to the reasons mentioned above u32 is required.
Quoted 8 lines
Quoted 7 lines
arch/arm/plat-omap/include/plat/gpmc.h +4
-0+u32 t_aavdh;/* address hold time */ +u32 t_iaa;/* initial access time */ +u32 t_oe;/* access time from OE assertion */ +u32 t_wpl;/* write assertion time */
Quoted 8 lines
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 201
Quoted 5 lines
arch/arm/plat-omap/include/plat/gpmc.h +5
-0+u8 cyc_aavdh_oe; +u8 cyc_aavdh_we; +u8 cyc_oe; +u8 cyc_wpl; +u32 cyc_iaa;May be I should look at an example, but it would be good to document what these
cyc_xxxparameters are/represent.
These are cycles counterpart of that of time, I will update it too.
Regards
Afzal
PATCH v7 8/11 ARM: OMAP2+: gpmc: generic timing calculation
Hi Afzal,
Quoted 46 lines · Afzal
Hi Jon,
Quoted 9 lines · Jon
Documentation/bus-devices/ti-gpmc.txt line 51
Quoted 3 lines · Afzal Mohammed
Documentation/bus-devices/ti-gpmc.txt new file +3
-0+Dependency of peripheral timings on gpmc timings: + +cs_on: t_ceasuThanks for adding these details. Could be good to clarify that the left-hand side parameters are the gpmc register fields and the right-hand side are the timing parameters these are calculated using.
Ok
Quoted 4 lines
Also, given that this is in documentation for completeness it could be good to somewhere state what "
t_ceasu" means. For the gpmc register field description may be we could give a reference to an OMAP document.Yes, it has been mentioned, as quoted below, reason it has not been mentioned here is to avoid duplication. I will add TRM reference.
"
Quoted 8 lines
Documentation/bus-devices/ti-gpmc.txt
Quoted 8 lines
Documentation/bus-devices/ti-gpmc.txt new file +6
-0+Note: Many of gpmc timings are dependent on other gpmc timings (a few +mentioned above, refer timing routine for more details. To know what +these peripheral timings correspond to, please see explanations in +struct gpmc_device_timings definition. +struct gpmc_device_timings { + u32 t_ceasu; /* address setup to CS valid */"
Quoted 7 lines
Documentation/bus-devices/ti-gpmc.txt line 58
Quoted 2 lines
Documentation/bus-devices/ti-gpmc.txt new file +2
-0+adv_rd_off: t_avdp_r, t_avdh(s*) +oe_on: t_oeasu, t_aavdh(a**), t_ach(s), cyc_aavdh_oe(s)Would it be better to have ...
oe_on(sync):t_oeasu,t_ach(*),cyc_aavdh_oeoe_on(async):t_oeasu,t_aavdh(*)Ok
Quoted 2 lines
* - optional
Quoted 7 lines
Quoted 4 lines
I assume that the hold times from the clock (
t_achandt_aavdh) are used for fine tuning if the peripheral requires this, but a user adding a new device would not be required to specify these, where ast_oeasuis mandatory.It depends on the peripheral,
t_oeasuin not used for OneNAND, tusb sync, so I prefer not mentioning any timing as optional or mandatory.
Ok.
Quoted 12 lines
Quoted 12 lines
Or maybe should the timings be grouped as ...
General
Read Async
Read Async Address/Data Multiplexed
Read Sync
Read Sync Address/Data Multiplexed
Write Async
Write Async Address/Data Multiplexed
Write Sync
Write Sync Address/Data Multiplexed
Quoted 5 lines
Quoted 2 lines
There may be some duplication but it will be clear where things like ADV timing applies.
I would prefer to keep it concise, but no strong opinion on it, if you prefer as above, I will change it.
I think that if these represent the main use-case configurations this could add some value.
Quoted 11 lines
Quoted 7 lines
Quoted 1 line
+/* can the cycles be avoided ? */
Nit should this be marked with a TODO?
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 927
Quoted 1 line
arch/arm/mach-omap2/gpmc.c +1
-0+/* mux check required ? */ Nit should this be marked with a TODO?
Marking XXX should Ok, right ?, reason is that they are not kept as TODO, but rather as pointers to may be possible improvements
Sure, I don't have strong feelings about it but I would hope that at some point this comment be removed.
Quoted 53 lines
Quoted 5 lines
Review
Quoted 1 line
(quoted diff) +1
-0+ gpmc_t->adv_rd_off = gpmc_round_ps_to_ticks(temp);Any reason why we can't return ns in the above function? Or make this function
gpmc_round_ps_to_ns()? Then we could avoid havinggpmc_convert_ps_to_ns()below.Calculation in ps is required to get more accurate results.
Calculating in ns was the reason for issue faced on N800 for Tony with previous version.
I will explain what would have happened with v6 on N800, i.e. using ns values,
Based on logs from Tony, gpmc clk was 9ns, actually it would have been somewhere around 9115ps.Take below timings of previous version in tusb async case
gpmc_t->oe_on = gpmc_round_ps_to_ticks(temp) / 1000; /* access */ temp = max_t(u32, dev_t->t_iaa, /* remove t_iaa in async ? */ gpmc_t->oe_on * 1000 + dev_t->t_oe); temp = max_t(u32, temp, gpmc_t->cs_on * 1000 + dev_t->t_ce); temp = max_t(u32, temp, gpmc_t->adv_on * 1000 + dev_t->t_aa); gpmc_t->access = gpmc_round_ps_to_ticks(temp) / 1000;Upon calculating we get,
oe_on= 63805 / 1000 = 63and for access (
t_oe= 300,t_ce=t_aa=t_iaa= 0),temp = 63 * 1000 + 300 = 63300
access = 63300 / 1000 = 63Here we get
oe_onas well as access as 7 ticks, but access should have been 8 ticks, which is what we will get by using ps values, i.e. as in this version, as below,gpmc_t->oe_on = gpmc_round_ps_to_ticks(temp); /* access */ temp = max_t(u32, dev_t->t_iaa, /* remove t_iaa in async ? */ gpmc_t->oe_on + dev_t->t_oe); temp = max_t(u32, temp, gpmc_t->cs_on + dev_t->t_ce); temp = max_t(u32, temp, gpmc_t->adv_on + dev_t->t_aa); gpmc_t->access = gpmc_round_ps_to_ticks(temp);
Quoted 1 line
I believe it is always better to go with higher resolution.
Ok, thanks for clarifying.
Quoted 7 lines
Quoted 3 lines
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 1209
Quoted 1 line
arch/arm/mach-omap2/gpmc.c +1
-0+gpmc_convert_ps_to_ns (gpmc_t);I am wondering if we could avoid this above function and then ...
This will be removed once it is confirmed that all the peripherals using custom runtime calculation can work with this generic routine. Then all calculation would be purely in ps.
Ok, great. May be add a TODO here to make this clear that this is temporary.
Quoted 4 lines
Right now converting ps to ns has been kept only to be compatible with custom routines and so that we can easily go back to custom routines in case of any issues, quoting relevant commit message below,
Quoted 10 lines
"
Timings are calculated in ps to prevent rounding errors and converted to ns at final stage so that these values can be directly fed togpmc_cs_set_timings().gpmc_cs_set_timings()would be modified to take ps once all custom timing routines are replaced by the generic routine, at the same time generic timing routine would be modified to provide timings in ps. structgpmc_timingsfield types are upgraded from u16 => u32 so that it can hold ps values.
"
Ok.
Quoted 28 lines
Quoted 8 lines
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 118
Quoted 6 lines
arch/arm/plat-omap/include/plat/gpmc.h +2
-2@@ -116,42 +116,103 @@ struct gpmc_timings { -u16 wr_access;/* WRACCESSTIME */ -u16 wr_data_mux_bus;/* WRDATAONADMUXBUS */ +u32 wr_access;/* WRACCESSTIME */ +u32 wr_data_mux_bus;/* WRDATAONADMUXBUS */ ... we could keep the above u16.
Due to the reasons mentioned above u32 is required.
Quoted 8 lines
Quoted 7 lines
arch/arm/plat-omap/include/plat/gpmc.h +4
-0+u32 t_aavdh;/* address hold time */ +u32 t_iaa;/* initial access time */ +u32 t_oe;/* access time from OE assertion */ +u32 t_wpl;/* write assertion time */ Quoted 8 lines
arch/arm/plat-omap/include/plat/gpmc.h struct gpmc_timings { · line 201
Quoted 5 lines
arch/arm/plat-omap/include/plat/gpmc.h +5
-0+u8 cyc_aavdh_oe; +u8 cyc_aavdh_we; +u8 cyc_oe; +u8 cyc_wpl; +u32 cyc_iaa;May be I should look at an example, but it would be good to document what these
cyc_xxxparameters are/represent.
Quoted 1 line
These are cycles counterpart of that of time, I will update it too.
Thanks!
Jon
PATCH v7 8/11 ARM: OMAP2+: gpmc: generic timing calculation
Hi Jon,
Quoted 14 lines · Jon
Quoted 12 lines · Afzal
Quoted 12 lines
Or maybe should the timings be grouped as ...
General
Read Async
Read Async Address/Data Multiplexed
Read Sync
Read Sync Address/Data Multiplexed
Write Async
Write Async Address/Data Multiplexed
Write Sync
Write Sync Address/Data Multiplexed
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
There may be some duplication but it will be clear where things like ADV timing applies.
I would prefer to keep it concise, but no strong opinion on it, if you prefer as above, I will change it.
I think that if these represent the main use-case configurations this could add some value.
Ok
Quoted 9 lines
Quoted 7 lines
Quoted 3 lines
arch/arm/mach-omap2/gpmc.c static void __init gpmc_mem_init(void) · line 1209
Quoted 1 line
arch/arm/mach-omap2/gpmc.c +1
-0+gpmc_convert_ps_to_ns (gpmc_t);I am wondering if we could avoid this above function and then ...
This will be removed once it is confirmed that all the peripherals using custom runtime calculation can work with this generic routine. Then all calculation would be purely in ps.
Ok, great. May be add a TODO here to make this clear that this is temporary.
Sure
Regards
Afzal
PATCH v7 9/11 ARM: OMAP2+: onenand: generic timing calculation
In reply to Afzal MohammedGeneric gpmc timing calculation helper is available now, use it instead of custom timing calculation.
--- arch/arm/mach-omap2/gpmc-onenand.c | 124 +++++++++++++------------------------ 1 file changed, 43 insertions(+), 81 deletions(-)
arch/arm/mach-omap2/gpmc-onenand.c +43 -81
@@ -49,6 +49,7 @@ static struct platform_device gpmc_onenand_device = {static struct gpmc_timings omap2_onenand_calc_async_timings (void ) { +struct gpmc_device_timings dev_t;struct gpmc_timings t;const int t_cer =15 ;
@@ -58,35 +59,24 @@ static struct gpmc_timings omap2_onenand_calc_async_timings(void)const int t_aa =76 ;const int t_oe =20 ;const int t_cez =20 ;/* max of t_cez, t_oez */ -const int t_ds =30 ;const int t_wpl =40 ;const int t_wph =30 ; -memset (&t,0 ,sizeof (t)); - t.sync_clk =0 ; - t.cs_on =0 ; - t.adv_on =0 ; - -/* Read */ - t.adv_rd_off =gpmc_round_ns_to_ticks (max_t (int, t_avdp, t_cer)); - t.oe_on = t.adv_rd_off +gpmc_round_ns_to_ticks (t_aavdh); - t.access = t.adv_on +gpmc_round_ns_to_ticks (t_aa); - t.access =max_t (int, t.access, t.cs_on +gpmc_round_ns_to_ticks (t_ce)); - t.access =max_t (int, t.access, t.oe_on +gpmc_round_ns_to_ticks (t_oe)); - t.oe_off = t.access +gpmc_round_ns_to_ticks (1 ); - t.cs_rd_off = t.oe_off; - t.rd_cycle = t.cs_rd_off +gpmc_round_ns_to_ticks (t_cez); - -/* Write */ - t.adv_wr_off = t.adv_rd_off; - t.we_on = t.oe_on; -if (cpu_is_omap34xx ()) { - t.wr_data_mux_bus = t.we_on; - t.wr_access = t.we_on +gpmc_round_ns_to_ticks (t_ds); - } - t.we_off = t.we_on +gpmc_round_ns_to_ticks (t_wpl); - t.cs_wr_off = t.we_off +gpmc_round_ns_to_ticks (t_wph); - t.wr_cycle = t.cs_wr_off +gpmc_round_ns_to_ticks (t_cez); +memset (&dev_t,0 ,sizeof (dev_t)); + + dev_t.mux = true; + dev_t.t_avdp_r =max_t (int, t_avdp, t_cer) *1000 ; + dev_t.t_avdp_w = dev_t.t_avdp_r; + dev_t.t_aavdh = t_aavdh *1000 ; + dev_t.t_aa = t_aa *1000 ; + dev_t.t_ce = t_ce *1000 ; + dev_t.t_oe = t_oe *1000 ; + dev_t.t_cez_r = t_cez *1000 ; + dev_t.t_cez_w = dev_t.t_cez_r; + dev_t.t_wpl = t_wpl *1000 ; + dev_t.t_wph = t_wph *1000 ; + +gpmc_calc_timings (&t, &dev_t);return t; }
@@ -172,16 +162,15 @@ static struct gpmc_timings omap2_onenand_calc_sync_timings(struct omap_onenand_platform_data *cfg, int freq) { +struct gpmc_device_timings dev_t;struct gpmc_timings t;const int t_cer =15 ;const int t_avdp =12 ;const int t_cez =20 ;/* max of t_cez, t_oez */ -const int t_ds =30 ;const int t_wpl =40 ;const int t_wph =30 ;int min_gpmc_clk_period, t_ces, t_avds, t_avdh, t_ach, t_aavdh, t_rdyo; -int div, fclk_offset_ns, fclk_offset, gpmc_clk_ns; -int ticks_cez; +int div, gpmc_clk_ns;if (cfg->flags &ONENAND_SYNC_READ ) onenand_flags =ONENAND_FLAG_SYNCREAD ;
@@ -248,62 +237,35 @@ omap2_onenand_calc_sync_timings(struct omap_onenand_platform_data *cfg, latency =4 ;/* Set synchronous read timings */ -memset (&t,0 ,sizeof (t)); - -if (div ==1 ) { - t.bool_timings.cs_extra_delay = true; - t.bool_timings.adv_extra_delay = true; - t.bool_timings.oe_extra_delay = true; - t.bool_timings.we_extra_delay = true; - } +memset (&dev_t,0 ,sizeof (dev_t)); - t.sync_clk = min_gpmc_clk_period; - t.cs_on =0 ; - t.adv_on =0 ; - fclk_offset_ns =gpmc_round_ns_to_ticks (max_t (int, t_ces, t_avds)); - fclk_offset =gpmc_ns_to_ticks (fclk_offset_ns); - t.page_burst_access = gpmc_clk_ns; - -/* Read */ - t.adv_rd_off =gpmc_ticks_to_ns (fclk_offset +gpmc_ns_to_ticks (t_avdh)); - t.oe_on =gpmc_ticks_to_ns (fclk_offset +gpmc_ns_to_ticks (t_ach)); -/* Force at least 1 clk between AVD High to OE Low */ -if (t.oe_on <= t.adv_rd_off) - t.oe_on = t.adv_rd_off +gpmc_round_ns_to_ticks (1 ); - t.access =gpmc_ticks_to_ns (fclk_offset + (latency +1 ) * div); - t.oe_off = t.access +gpmc_round_ns_to_ticks (1 ); - t.cs_rd_off = t.oe_off; - ticks_cez = ((gpmc_ns_to_ticks (t_cez) + div -1 ) / div) * div; - t.rd_cycle =gpmc_ticks_to_ns (fclk_offset + (latency +1 ) * div + - ticks_cez); - - t.clk_activation = fclk_offset_ns; - -/* Write */ + dev_t.mux = true; + dev_t.sync_read = true;if (onenand_flags &ONENAND_FLAG_SYNCWRITE ) { - t.adv_wr_off = t.adv_rd_off; - t.we_on =0 ; - t.we_off = t.cs_rd_off; - t.cs_wr_off = t.cs_rd_off; - t.wr_cycle = t.rd_cycle; -if (cpu_is_omap34xx ()) { - t.wr_data_mux_bus =gpmc_ticks_to_ns (fclk_offset + -gpmc_ps_to_ticks (min_gpmc_clk_period + - t_rdyo *1000 )); - t.wr_access = t.access; - } + dev_t.sync_write = true; }else { - t.adv_wr_off =gpmc_round_ns_to_ticks (max_t (int, - t_avdp, t_cer)); - t.we_on = t.adv_wr_off +gpmc_round_ns_to_ticks (t_aavdh); - t.we_off = t.we_on +gpmc_round_ns_to_ticks (t_wpl); - t.cs_wr_off = t.we_off +gpmc_round_ns_to_ticks (t_wph); - t.wr_cycle = t.cs_wr_off +gpmc_round_ns_to_ticks (t_cez); -if (cpu_is_omap34xx ()) { - t.wr_data_mux_bus = t.we_on; - t.wr_access = t.we_on +gpmc_round_ns_to_ticks (t_ds); - } + dev_t.t_avdp_w =max (t_avdp, t_cer) *1000 ; + dev_t.t_wpl = t_wpl *1000 ; + dev_t.t_wph = t_wph *1000 ; + dev_t.t_aavdh = t_aavdh *1000 ; } + dev_t.ce_xdelay = true; + dev_t.avd_xdelay = true; + dev_t.oe_xdelay = true; + dev_t.we_xdelay = true; + dev_t.clk = min_gpmc_clk_period; + dev_t.t_bacc = dev_t.clk; + dev_t.t_ces = t_ces *1000 ; + dev_t.t_avds = t_avds *1000 ; + dev_t.t_avdh = t_avdh *1000 ; + dev_t.t_ach = t_ach *1000 ; + dev_t.cyc_iaa = (latency +1 ); + dev_t.t_cez_r = t_cez *1000 ; + dev_t.t_cez_w = dev_t.t_cez_r; + dev_t.cyc_aavdh_oe =1 ; + dev_t.t_rdyo = t_rdyo *1000 + min_gpmc_clk_period; + +gpmc_calc_timings (&t, &dev_t);return t; }
Signature · 1 line
1.7.12
PATCH v7 10/11 ARM: OMAP2+: smc91x: generic timing calculation
In reply to Afzal MohammedGeneric gpmc timing calculation helper is available now, use it instead of custom timing calculation.
--- arch/arm/mach-omap2/gpmc-smc91x.c | 43 ++++++++++++++++----------------------- 1 file changed, 17 insertions(+), 26 deletions(-)
arch/arm/mach-omap2/gpmc-smc91x.c +17 -26
@@ -58,6 +58,7 @@ static struct platform_device gpmc_smc91x_device = {static int smc91c96_gpmc_retime (void ) {struct gpmc_timings t; +struct gpmc_device_timings dev_t;const int t3 =10 ;/* Figure 12.2 read and 12.4 write */ const int t4_r =20 ;/* Figure 12.2 read */ const int t4_w =5 ;/* Figure 12.4 write */
@@ -68,32 +69,6 @@ static int smc91c96_gpmc_retime(void)const int t20 =185 ;/* Figure 12.2 read and 12.4 write */ u32 l; -memset (&t,0 ,sizeof (t)); - -/* Read timings */ - t.cs_on =0 ; - t.adv_on = t.cs_on; - t.oe_on = t.adv_on + t3; - t.access = t.oe_on + t5; - t.oe_off = t.access; - t.adv_rd_off = t.oe_off +max (t4_r, t6); - t.cs_rd_off = t.oe_off; - t.rd_cycle = t20 - t.oe_on; - -/* Write timings */ - t.we_on = t.adv_on + t3; - -if (cpu_is_omap34xx () && (gpmc_cfg->flags &GPMC_MUX_ADD_DATA )) { - t.wr_data_mux_bus = t.we_on; - t.we_off = t.wr_data_mux_bus + t7; - }else - t.we_off = t.we_on + t7; -if (cpu_is_omap34xx ()) - t.wr_access = t.we_off; - t.adv_wr_off = t.we_off +max (t4_w, t8); - t.cs_wr_off = t.we_off + t4_w; - t.wr_cycle = t20 - t.we_on; - l =GPMC_CONFIG1_DEVICESIZE_16 ;if (gpmc_cfg->flags &GPMC_MUX_ADD_DATA ) l |=GPMC_CONFIG1_MUXADDDATA ;
@@ -115,6 +90,22 @@ static int smc91c96_gpmc_retime(void)if (gpmc_cfg->flags &GPMC_MUX_ADD_DATA )return 0 ; +memset (&dev_t,0 ,sizeof (dev_t)); + + dev_t.t_oeasu = t3 *1000 ; + dev_t.t_oe = t5 *1000 ; + dev_t.t_cez_r = t4_r *1000 ; + dev_t.t_oez = t6 *1000 ; + dev_t.t_rd_cycle = (t20 - t3) *1000 ; + + dev_t.t_weasu = t3 *1000 ; + dev_t.t_wpl = t7 *1000 ; + dev_t.t_wph = t8 *1000 ; + dev_t.t_cez_w = t4_w *1000 ; + dev_t.t_wr_cycle = (t20 - t3) *1000 ; + +gpmc_calc_timings (&t, &dev_t); +return gpmc_cs_set_timings (gpmc_cfg->cs, &t); }
Signature · 1 line
1.7.12
PATCH v7 11/11 ARM: OMAP2+: tusb6010: generic timing calculation
In reply to Afzal MohammedGeneric gpmc timing calculation helper is available now, use it instead of custom timing calculation.
--- arch/arm/mach-omap2/usb-tusb6010.c | 182 +++++++++---------------------------- 1 file changed, 44 insertions(+), 138 deletions(-)
arch/arm/mach-omap2/usb-tusb6010.c +44 -138
@@ -26,182 +26,88 @@ static u8 async_cs, sync_cs;static unsigned refclk_psec; -/* t2_ps, when quantized to fclk units, must happen no earlier than -* the clock after after t1_NS. -* -* Return a possibly updated value of t2_ps, converted to nsec. -*/ -static unsigned -next_clk (unsigned t1_NS,unsigned t2_ps,unsigned fclk_ps) -{ -unsigned t1_ps = t1_NS *1000 ; -unsigned t1_f, t2_f; - -if ((t1_ps + fclk_ps) < t2_ps) -return t2_ps /1000 ; - - t1_f = (t1_ps + fclk_ps -1 ) / fclk_ps; - t2_f = (t2_ps + fclk_ps -1 ) / fclk_ps; - -if (t1_f >= t2_f) - t2_f = t1_f +1 ; - -return (t2_f * fclk_ps) /1000 ; -} -/* NOTE: timings are from tusb 6010 datasheet Rev 1.8, 12-Sept 2006 */ -static int tusb_set_async_mode (unsigned sysclk_ps,unsigned fclk_ps) +static int tusb_set_async_mode (unsigned sysclk_ps) { +struct gpmc_device_timings dev_t;struct gpmc_timings t;unsigned t_acsnh_advnh = sysclk_ps +3000 ; -unsigned tmp; - -memset (&t,0 ,sizeof (t)); - -/* CS_ON = t_acsnh_acsnl */ - t.cs_on =8 ; -/* ADV_ON = t_acsnh_advnh - t_advn */ - t.adv_on =next_clk (t.cs_on, t_acsnh_advnh -7000 , fclk_ps); - -/* -* READ ... from omap2420 TRM fig 12-13 -*/ - -/* ADV_RD_OFF = t_acsnh_advnh */ - t.adv_rd_off =next_clk (t.adv_on, t_acsnh_advnh, fclk_ps); - -/* OE_ON = t_acsnh_advnh + t_advn_oen (then wait for nRDY) */ - t.oe_on =next_clk (t.adv_on, t_acsnh_advnh +1000 , fclk_ps); - -/* ACCESS = counters continue only after nRDY */ - tmp = t.oe_on *1000 +300 ; - t.access =next_clk (t.oe_on, tmp, fclk_ps); - -/* OE_OFF = after data gets sampled */ - tmp = t.access *1000 ; - t.oe_off =next_clk (t.access, tmp, fclk_ps); - - t.cs_rd_off = t.oe_off; - - tmp = t.cs_rd_off *1000 +7000 /* t_acsn_rdy_z */ ; - t.rd_cycle =next_clk (t.cs_rd_off, tmp, fclk_ps); - -/* -* WRITE ... from omap2420 TRM fig 12-15 -*/ -/* ADV_WR_OFF = t_acsnh_advnh */ - t.adv_wr_off = t.adv_rd_off; +memset (&dev_t,0 ,sizeof (dev_t)); -/* WE_ON = t_acsnh_advnh + t_advn_wen (then wait for nRDY) */ - t.we_on =next_clk (t.adv_wr_off, t_acsnh_advnh +1000 , fclk_ps); + dev_t.mux = true; -/* WE_OFF = after data gets sampled */ - tmp = t.we_on *1000 +300 ; - t.we_off =next_clk (t.we_on, tmp, fclk_ps); + dev_t.t_ceasu =8 *1000 ; + dev_t.t_avdasu = t_acsnh_advnh -7000 ; + dev_t.t_ce_avd =1000 ; + dev_t.t_avdp_r = t_acsnh_advnh; + dev_t.t_oeasu = t_acsnh_advnh +1000 ; + dev_t.t_oe =300 ; + dev_t.t_cez_r =7000 ; + dev_t.t_cez_w = dev_t.t_cez_r; + dev_t.t_avdp_w = t_acsnh_advnh; + dev_t.t_weasu = t_acsnh_advnh +1000 ; + dev_t.t_wpl =300 ; + dev_t.cyc_aavdh_we =1 ; - t.cs_wr_off = t.we_off; - - tmp = t.cs_wr_off *1000 +7000 /* t_acsn_rdy_z */ ; - t.wr_cycle =next_clk (t.cs_wr_off, tmp, fclk_ps); +gpmc_calc_timings (&t, &dev_t);return gpmc_cs_set_timings (async_cs, &t); } -static int tusb_set_sync_mode (unsigned sysclk_ps,unsigned fclk_ps) +static int tusb_set_sync_mode (unsigned sysclk_ps) { +struct gpmc_device_timings dev_t;struct gpmc_timings t;unsigned t_scsnh_advnh = sysclk_ps +3000 ; -unsigned tmp; - -memset (&t,0 ,sizeof (t)); - t.cs_on =8 ; - -/* ADV_ON = t_acsnh_advnh - t_advn */ - t.adv_on =next_clk (t.cs_on, t_scsnh_advnh -7000 , fclk_ps); - -/* GPMC_CLK rate = fclk rate / div */ - t.sync_clk =11100 /* 11.1 nsec */ ; - tmp = (t.sync_clk + fclk_ps -1 ) / fclk_ps; -if (tmp >4 ) -return -ERANGE ; -if (tmp ==0 ) - tmp =1 ; - t.page_burst_access = (fclk_ps * tmp) /1000 ; - -/* -* READ ... based on omap2420 TRM fig 12-19, 12-20 -*/ - -/* ADV_RD_OFF = t_scsnh_advnh */ - t.adv_rd_off =next_clk (t.adv_on, t_scsnh_advnh, fclk_ps); - -/* OE_ON = t_scsnh_advnh + t_advn_oen * fclk_ps (then wait for nRDY) */ - tmp = (t.adv_rd_off *1000 ) + (3 * fclk_ps); - t.oe_on =next_clk (t.adv_on, tmp, fclk_ps); - -/* ACCESS = number of clock cycles after t_adv_eon */ - tmp = (t.oe_on *1000 ) + (5 * fclk_ps); - t.access =next_clk (t.oe_on, tmp, fclk_ps); - -/* OE_OFF = after data gets sampled */ - tmp = (t.access *1000 ) + (1 * fclk_ps); - t.oe_off =next_clk (t.access, tmp, fclk_ps); - t.cs_rd_off = t.oe_off; - - tmp = t.cs_rd_off *1000 +7000 /* t_scsn_rdy_z */ ; - t.rd_cycle =next_clk (t.cs_rd_off, tmp, fclk_ps); - -/* -* WRITE ... based on omap2420 TRM fig 12-21 -*/ - -/* ADV_WR_OFF = t_scsnh_advnh */ - t.adv_wr_off = t.adv_rd_off; - -/* WE_ON = t_scsnh_advnh + t_advn_wen * fclk_ps (then wait for nRDY) */ - tmp = (t.adv_wr_off *1000 ) + (3 * fclk_ps); - t.we_on =next_clk (t.adv_wr_off, tmp, fclk_ps); - -/* WE_OFF = number of clock cycles after t_adv_wen */ - tmp = (t.we_on *1000 ) + (6 * fclk_ps); - t.we_off =next_clk (t.we_on, tmp, fclk_ps); - - t.cs_wr_off = t.we_off; - - tmp = t.cs_wr_off *1000 +7000 /* t_scsn_rdy_z */ ; - t.wr_cycle =next_clk (t.cs_wr_off, tmp, fclk_ps); - - t.clk_activation =gpmc_ticks_to_ns (1 ); +memset (&dev_t,0 ,sizeof (dev_t)); + + dev_t.mux = true; + dev_t.sync_read = true; + dev_t.sync_write = true; + + dev_t.clk =11100 ; + dev_t.t_bacc =1000 ; + dev_t.t_ces =1000 ; + dev_t.t_ceasu =8 *1000 ; + dev_t.t_avdasu = t_scsnh_advnh -7000 ; + dev_t.t_ce_avd =1000 ; + dev_t.t_avdp_r = t_scsnh_advnh; + dev_t.cyc_aavdh_oe =3 ; + dev_t.cyc_oe =5 ; + dev_t.t_ce_rdyz =7000 ; + dev_t.t_avdp_w = t_scsnh_advnh; + dev_t.cyc_aavdh_we =3 ; + dev_t.cyc_wpl =6 ; + dev_t.t_ce_rdyz =7000 ; + +gpmc_calc_timings (&t, &dev_t);return gpmc_cs_set_timings (sync_cs, &t); } -extern unsigned long gpmc_get_fclk_period (void ); -/* tusb driver calls this when it changes the chip's clocking */ int tusb6010_platform_retime (unsigned is_refclk) {static const char error[] =KERN_ERR "tusb6010 %s retime error %d\n" ; -unsigned fclk_ps =gpmc_get_fclk_period ();unsigned sysclk_ps;int status; -if (!refclk_psec || fclk_ps ==0 ) +if (!refclk_psec)return -ENODEV ; sysclk_ps = is_refclk ? refclk_psec :TUSB6010_OSCCLK_60 ; - status =tusb_set_async_mode (sysclk_ps, fclk_ps); + status =tusb_set_async_mode (sysclk_ps);if (status <0 ) {printk (error,"async" , status); goto done; } - status =tusb_set_sync_mode (sysclk_ps, fclk_ps); + status =tusb_set_sync_mode (sysclk_ps);if (status <0 )printk (error,"sync" , status); done:
Signature · 1 line
1.7.12
Tony Lindgren
maintainerv7 cover OMAP-GPMC: generic time calc, prepare for driver
In reply to Afzal MohammedQuoted 11 lines · Afzal Mohammed
Hi,
This version - v7 as compared to previous version, takes care of rounding issues due to the usage of nanoseconds in generic timing routine. All calculations are now in picoseconds. Once all timings are calculated it is converted to nanoseconds so that calculated timing values are compatible with existing custom timing routines (this will help in reverting back to custom routines easily in case of any issues). And documentation has been added on gpmc timings. Also redundant rounding of nand timings has been removed as part of this series.
I gave this series a quick test on my n800 after applying the two serial patches needed to get the uart to work, and it seems to be working just fine.
Was there still some discussion on the format of the generic timings that's still pending? I think Jon made some comments on the format?
Regards,
Tony
v7 cover OMAP-GPMC: generic time calc, prepare for driver
Hi Tony,
Quoted 7 lines · Tony Lindgren
I gave this series a quick test on my n800 after applying the two serial patches needed to get the uart to work, and it seems to be working just fine.
Was there still some discussion on the format of the generic timings that's still pending? I think Jon made some comments on the format?
What I deduced finally from Jon's replies was that he wanted more documentation on generic timings, and that has been added in this series.
Regards
Afzal
Tony Lindgren
maintainerv7 cover OMAP-GPMC: generic time calc, prepare for driver
Quoted 8 lines · Mohammed, Afzal
Hi Tony,
Quoted 4 lines · Tony Lindgren
I gave this series a quick test on my n800 after applying the two serial patches needed to get the uart to work, and it seems to be working just fine.
Quoted 7 lines
Quoted 3 lines
Was there still some discussion on the format of the generic timings that's still pending? I think Jon made some comments on the format?
What I deduced finally from Jon's replies was that he wanted more documentation on generic timings, and that has been added in this series.
OK let's see if he has other pending comments next week.
Regards,
Tony