AM3505/3517 ZCN package support

PATCH In review Raphaël Assénat 2 participants 5 messages Jul 6, 2011 – Jul 8, 2011

Subsystems (3)

Arm (32-bit) Arm sub-architectures OMAP2+ support

lore

Share & tools

lore

Raphaël Assénat

author

2011-07-06 16:52 UTC #0 lore raw

PATCH v2 1/1 AM3505/3517 ZCN package support

Fixes according to Sanjeev's comments in previous thread.

---
This patch adds support for the AM35xx ZCN package specific muxmodes.

Signed-off-by Raphael Assenat <[email protected]>

arch/arm/mach-omap2/Kconfig +3 -0

index 4ae6257..bf452eb 100644
@@ -103,6 +103,9 @@ config OMAP_PACKAGE_CBL
 config OMAP_PACKAGE_CBS
        bool
 
+config OMAP_PACKAGE_ZCN
+       bool
+
 comment "OMAP Board Type"
 	depends on ARCH_OMAP2PLUS

arch/arm/mach-omap2/mux.h +1 -0

index 2132308..f227503 100644
@@ -62,6 +62,7 @@
 
 /* Flags for omapX_mux_init */
 #define OMAP_PACKAGE_MASK		0xffff
+#define OMAP_PACKAGE_ZCN		9		/* 491-pin 0.65 */
 #define OMAP_PACKAGE_CBS		8		/* 547-pin 0.40 0.40 */
 #define OMAP_PACKAGE_CBL		7		/* 547-pin 0.40 0.40 */
 #define OMAP_PACKAGE_CBP		6		/* 515-pin 0.40 0.50 */

arch/arm/mach-omap2/mux34xx.c +567 -0

585 lines not on this page · raw message

arch/arm/mach-omap2/mux34xx.h +36 -0

index 6543ebf..5626544 100644
@@ -316,6 +316,42 @@
 #define OMAP3_CONTROL_PADCONF_SDRC_CKE0_OFFSET			0x232
 #define OMAP3_CONTROL_PADCONF_SDRC_CKE1_OFFSET			0x234
 
+/* AM3505/3517 only */
+#define OMAP3_CONTROL_PADCONF_CCDC_PCLK_OFFSET			0x1b4
+#define OMAP3_CONTROL_PADCONF_CCDC_FIELD_OFFSET			0x1b6
+#define OMAP3_CONTROL_PADCONF_CCDC_HD_OFFSET			0x1b8
+#define OMAP3_CONTROL_PADCONF_CCDC_VD_OFFSET			0x1ba
+#define OMAP3_CONTROL_PADCONF_CCDC_WEN_OFFSET			0x1bc
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA0_OFFSET			0x1be
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA1_OFFSET			0x1c0
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA2_OFFSET			0x1c2
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA3_OFFSET			0x1c4
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA4_OFFSET			0x1c6
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA5_OFFSET			0x1c8
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA6_OFFSET			0x1ca
+#define OMAP3_CONTROL_PADCONF_CCDC_DATA7_OFFSET			0x1cc
+#define OMAP3_CONTROL_PADCONF_RMII_MDIO_DATA_OFFSET		0x1ce
+#define OMAP3_CONTROL_PADCONF_RMII_MDIO_CLK_OFFSET		0x1d0
+#define OMAP3_CONTROL_PADCONF_RMII_RXD0_OFFSET			0x1d2
+#define OMAP3_CONTROL_PADCONF_RMII_RXD1_OFFSET			0x1d4
+#define OMAP3_CONTROL_PADCONF_RMII_CRS_DV_OFFSET		0x1d6
+#define OMAP3_CONTROL_PADCONF_RMII_RXER_OFFSET			0x1d8
+#define OMAP3_CONTROL_PADCONF_RMII_TXD0_OFFSET			0x1da
+#define OMAP3_CONTROL_PADCONF_RMII_TXD1_OFFSET			0x1dc
+#define OMAP3_CONTROL_PADCONF_RMII_TXEN_OFFSET			0x1de
+#define OMAP3_CONTROL_PADCONF_RMII_50MHZ_CLK_OFFSET		0x1e0
+#define OMAP3_CONTROL_PADCONF_USB0_DRVVBUS_OFFSET		0x1e2
+#define OMAP3_CONTROL_PADCONF_HECC1_TXD_OFFSET			0x1e4
+#define OMAP3_CONTROL_PADCONF_HECC1_RXD_OFFSET			0x1e6
+#define OMAP3_CONTROL_PADCONF_SYS_BOOT7_OFFSET			0x1e8
+#define OMAP3_CONTROL_PADCONF_SDRC_DQS0N_OFFSET			0x1ea
+#define OMAP3_CONTROL_PADCONF_SDRC_DQS1N_OFFSET			0x1ec
+#define OMAP3_CONTROL_PADCONF_SDRC_DQS2N_OFFSET			0x1ee
+#define OMAP3_CONTROL_PADCONF_SDRC_DQS3N_OFFSET			0x1f0
+#define OMAP3_CONTROL_PADCONF_SDRC_STRBEN_DLY0_OFFSET		0x1f2
+#define OMAP3_CONTROL_PADCONF_SDRC_STRBEN_DLY1_OFFSET		0x1f4
+#define OMAP3_CONTROL_PADCONF_SYS_BOOT8_OFFSET			0x1f6
+
 /* 36xx only */
 #define OMAP3_CONTROL_PADCONF_GPMC_A11_OFFSET			0x236
 #define OMAP3_CONTROL_PADCONF_SDRC_BA0_OFFSET			0x570

Tony Lindgren

maintainer

2011-07-07 14:20 UTC #1 lore raw

Quoted 4 lines · Raphaël Assénat

Fixes according to Sanjeev's comments in previous thread.
---
This patch adds support for the AM35xx ZCN package specific muxmodes.

Thanks for doing this. Still it's quite a few lines of data.. So I suggest that we just plan on doing the mux data for v3.2 merge window in device tree format. I'm planning on working on that after v3.1 merge window and should be able to generate it for am3505 using your patch.

Otherwise we'll be patching something that will be disappearing quite soon anyways.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Raphaël Assénat

author

2011-07-07 14:41 UTC #2 lore raw

Quoted 11 lines · Tony Lindgren

Quoted 4 lines · Raphaël Assénat
Fixes according to Sanjeev's comments in previous thread.
---
This patch adds support for the AM35xx ZCN package specific muxmodes.
Thanks for doing this. Still it's quite a few lines of data.. So I suggest that we just plan on doing the mux data for v3.2 merge window in device tree format. I'm planning on working on that after v3.1 merge window and should be able to generate it for am3505 using your patch.

Ok, looking forward to testing this.

Quoted 2 lines

Otherwise we'll be patching something that will be disappearing quite soon anyways.

I agree. At least in the meantime my problem is fixed by this patch.

This is unrelated to this thread but..
do you think we could merge this one?

[PATCH 5/5] am3505/3517: Various platform defines for UART4
http://marc.info/?l=linux-omap&m=130980816418020&w=4

It does not depend on the other patches in this set so it can be applied individually. And those definitions will be needed later when full am35xx support is implemented anyway.

Best regards,
Raphaël Assénat
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Tony Lindgren

maintainer

2011-07-07 15:35 UTC #3 lore raw

Quoted 12 lines · Raphaël Assénat

Quoted 11 lines · Tony Lindgren
Quoted 4 lines · Raphaël Assénat
Fixes according to Sanjeev's comments in previous thread.
---
This patch adds support for the AM35xx ZCN package specific muxmodes.
Thanks for doing this. Still it's quite a few lines of data.. So I suggest that we just plan on doing the mux data for v3.2 merge window in device tree format. I'm planning on working on that after v3.1 merge window and should be able to generate it for am3505 using your patch.

Quoted 5 lines

Ok, looking forward to testing this.
Quoted 2 lines
Otherwise we'll be patching something that will be disappearing quite soon anyways.
I agree. At least in the meantime my problem is fixed by this patch.

OK, let's do that then.

Quoted 9 lines

This is unrelated to this thread but..
do you think we could merge this one?
[PATCH 5/5] am3505/3517: Various platform defines for UART4
http://marc.info/?l=linux-omap&m=130980816418020&w=4
It does not depend on the other patches in this set so it can be applied individually. And those definitions will be needed later when full am35xx support is implemented anyway.

Yes that looks good to me, will queue. Do you have some other bits in your patches that could be merged?

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Raphaël Assénat

author

2011-07-08 17:11 UTC #4 lore raw

Quoted 7 lines · Tony Lindgren

Quoted 6 lines · Raphaël Assénat
This is unrelated to this thread but..
do you think we could merge this one?
[PATCH 5/5] am3505/3517: Various platform defines for UART4
http://marc.info/?l=linux-omap&m=130980816418020&w=4

Quoted 6 lines

Quoted 3 lines
It does not depend on the other patches in this set so it can be applied individually. And those definitions will be needed later when full am35xx support is implemented anyway.
Yes that looks good to me, will queue. Do you have some other bits in your patches that could be merged?

Yes, I think also this one:

[PATCH 4/5] am3505/3517: UART4 fclk
http://marc.info/?l=linux-omap&m=130980809317954&w=2