From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Estevam Subject: Re: device tree binding documentation outdated Date: Wed, 2 Oct 2013 23:21:56 -0300 Message-ID: References: <20130927174916.GD12758@n2100.arm.linux.org.uk> <20130927190546.GG12758@n2100.arm.linux.org.uk> <20130927202110.GI12758@n2100.arm.linux.org.uk> <20130928083859.GQ12758@n2100.arm.linux.org.uk> <20130929061303.GB26156@S2101-09.ap.freescale.net> <20131002193316.GR12758@n2100.arm.linux.org.uk> <20131002234911.GD12758@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20131002234911.GD12758-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Russell King - ARM Linux Cc: Shawn Guo , "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Matt Sealey List-Id: devicetree@vger.kernel.org On Wed, Oct 2, 2013 at 8:49 PM, Russell King - ARM Linux wrote: > This apparantly is done by configuring the PLL on the IMX6 to 25MHz and > getting it to output it on this pin, and that is done in the freescale > BSP by this pin control setting: > > MX6DL_PAD_GPIO_16__ENET_ANATOP_ETHERNET_REF_OUT > > Now, if you look up that in the 4.1.0 BSP: > > #define MX6DL_PAD_GPIO_16__ENET_ANATOP_ETHERNET_REF_OUT \ > IOMUX_PAD(0x05E4, 0x0214, 0x12, 0x080C, 0, NO_PAD_CTRL) > > and that says to write 0x12 to 0x20e0000 + 0x214 - the > IOMUXC_SW_MUX_CTL_PAD_GPIO16 register. This name clearly implies that > the IMX6 is _outputting_ the reference clock. The register values here > selects MUX_MODE 2 (ENET_REF_CLK) _with_ SION set. There is no > configuration in this BSP for GPIO 16 in mux mode 2 without SION set. SION bit is set for this pad in mainline as well: MX6QDL_PAD_GPIO_16__ENET_REF_CLK 0x4001b0a8 (bit 30 is set, which indicates SION). -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html