From: joerg.krause@embedded.rocks (Jörg Krause)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND] ARM: dts: imx6ul: add missing OSC32K_32K_OUT mux mode
Date: Thu, 18 Jan 2018 10:27:45 +0100 [thread overview]
Message-ID: <1516267665.3727.4.camel@embedded.rocks> (raw)
In-Reply-To: <1516265435.7607.1.camel@pengutronix.de>
Hi Philipp,
On Thu, 2018-01-18 at 09:50 +0100, Philipp Zabel wrote:
> On Thu, 2018-01-18 at 09:25 +0100, J?rg Krause wrote:
> > Hi,
> >
> > On Thu, 2018-01-18 at 00:23 +0100, J?rg Krause wrote:
> > > RESEND because of missing Ccs. Original patch is [0].
> > >
> > > The 32 kHz reference clock on the i.MX6UL(L) can be output by
> > > setting the external signal XTALOSC_REF_CLK_32K in one of the
> > > following ways [1]:
> > >
> > > > ----------------------------------------------------------|
> > > > Signal | Pad | Mode | Direction |
> > > > ----------------------------------------------------------|
> > > > XTALOSC_REF_CLK_32K | ENET1_RX_EN | ALT2 | O |
> > > > | GPIO1_IO03 | ALT3 | |
> > > > | JTAG_TCK | ALT6 | |
> > > > ----------------------------------------------------------|
> > >
> > > [0] https://patchwork.ozlabs.org/patch/816108/
> > > [1] IMX6ULRM, Rev. 1, 04/2016, Table 58-1
> > >
> > > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > > ---
> > > arch/arm/boot/dts/imx6ul-pinfunc.h | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/arch/arm/boot/dts/imx6ul-pinfunc.h b/arch/arm/boot/dts/imx6ul-pinfunc.h
> > > index 0034eeb84542..e12654018c23 100644
> > > --- a/arch/arm/boot/dts/imx6ul-pinfunc.h
> > > +++ b/arch/arm/boot/dts/imx6ul-pinfunc.h
> > > @@ -63,6 +63,7 @@
> > > #define MX6UL_PAD_JTAG_TCK__SAI2_RX_DATA 0x0054 0x02e0 0x05f4 2 0
> > > #define MX6UL_PAD_JTAG_TCK__PWM7_OUT 0x0054 0x02e0 0x0000 4 0
> > > #define MX6UL_PAD_JTAG_TCK__GPIO1_IO14 0x0054 0x02e0 0x0000 5 0
> > > +#define MX6UL_PAD_JTAG_TCK__OSC32K_32K_OUT 0x0054 0x02e0 0x0000 6 0
> > > #define MX6UL_PAD_JTAG_TCK__SIM2_POWER_FAIL 0x0054 0x02e0 0x0000 8 0
> > > #define MX6UL_PAD_JTAG_TRST_B__SJC_TRSTB 0x0058 0x02e4 0x0000 0 0
> > > #define MX6UL_PAD_JTAG_TRST_B__GPT2_COMPARE3 0x0058 0x02e4 0x0000 1 0
> > > @@ -101,6 +102,7 @@
> > > #define MX6UL_PAD_GPIO1_IO03__I2C1_SDA 0x0068 0x02f4 0x05a8 0 1
> > > #define MX6UL_PAD_GPIO1_IO03__GPT1_COMPARE3 0x0068 0x02f4 0x0000 1 0
> > > #define MX6UL_PAD_GPIO1_IO03__USB_OTG2_OC 0x0068 0x02f4 0x0660 2 0
> > > +#define MX6UL_PAD_GPIO1_IO03__OSC32K_32K_OUT 0x0068 0x02f4 0x0000 3 0
> > > #define MX6UL_PAD_GPIO1_IO03__USDHC1_CD_B 0x0068 0x02f4 0x0668 4 0
> > > #define MX6UL_PAD_GPIO1_IO03__GPIO1_IO03 0x0068 0x02f4 0x0000 5 0
> > > #define MX6UL_PAD_GPIO1_IO03__CCM_DI0_eXT_CLK 0x0068 0x02f4 0x0000 6 0
> > > @@ -316,6 +318,7 @@
> > > #define MX6UL_PAD_ENET1_RX_EN__ENET1_RX_EN 0x00cc 0x0358 0x0000 0 0
> > > #define MX6UL_PAD_ENET1_RX_EN__UART5_DCE_RTS 0x00cc 0x0358 0x0640 1 3
> > > #define MX6UL_PAD_ENET1_RX_EN__UART5_DTE_CTS 0x00cc 0x0358 0x0000 1 0
> > > +#define MX6UL_PAD_ENET1_RX_EN__OSC32K_32K_OUT 0x00cc 0x0358 0x0000 2 0
> > > #define MX6UL_PAD_ENET1_RX_EN__CSI_DATA18 0x00cc 0x0358 0x0000 3 0
> > > #define MX6UL_PAD_ENET1_RX_EN__FLEXCAN2_TX 0x00cc 0x0358 0x0000 4 0
> > > #define MX6UL_PAD_ENET1_RX_EN__GPIO2_IO02 0x00cc 0x0358 0x0000 5 0
> >
> > Just noticed the pin is named REF_CLK_32K instead of OSC32K_32K_OUT in
> > the vendor Linux kernel. So better use their pin naming, right?
>
> The i.MX 6UltraLite Applications Processor Reference Manual, Rev. 1
> (Chapters 30.5.17, SW_MUX_CTL_PAD_JTAG_TCK SW MUX Control Register, and
> 30.5.47, SW_MUX_CTL_PAD_ENET1_RX_EN SW MUX Control Register) calls this
> OSC32K_32K_OUT.
Thanks for the reference! I guess this is why I named it this way in
the first place.
J?rg
next prev parent reply other threads:[~2018-01-18 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 23:23 [PATCH RESEND] ARM: dts: imx6ul: add missing OSC32K_32K_OUT mux mode Jörg Krause
2018-01-18 8:25 ` Jörg Krause
2018-01-18 8:50 ` Philipp Zabel
2018-01-18 9:27 ` Jörg Krause [this message]
2018-02-05 5:38 ` Shawn Guo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1516267665.3727.4.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox