From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] mx6sx: pins: Enable SION for I2C3 iomux setting
Date: Thu, 29 Jan 2015 18:54:17 +0100 [thread overview]
Message-ID: <54CA73C9.4000806@denx.de> (raw)
In-Reply-To: <54B3A3D8.7010208@mail.bg>
Hi,
On 12/01/2015 11:37, Nikolay Dimitrov wrote:
> Hi Ye.Li,
>
> On 01/12/2015 10:46 AM, Ye.Li wrote:
>> The I2C SDA and SCL require the IOMUX SION bit set to get input signal.
>>
>> Signed-off-by: Ye.Li <B37916@freescale.com>
>> ---
>> arch/arm/include/asm/arch-mx6/mx6sx_pins.h | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/include/asm/arch-mx6/mx6sx_pins.h
>> b/arch/arm/include/asm/arch-mx6/mx6sx_pins.h
>> index 7c6c1e8..da8c698 100644
>> --- a/arch/arm/include/asm/arch-mx6/mx6sx_pins.h
>> +++ b/arch/arm/include/asm/arch-mx6/mx6sx_pins.h
>> @@ -420,7 +420,7 @@ enum {
>>
>> MX6_PAD_KEY_COL4__KPP_COL_4 =
>> IOMUX_PAD(0x03FC, 0x00B4, 0, 0x0000, 0, 0),
>> MX6_PAD_KEY_COL4__ENET2_MDC =
>> IOMUX_PAD(0x03FC, 0x00B4, 1, 0x0000, 0, 0),
>> - MX6_PAD_KEY_COL4__I2C3_SCL =
>> IOMUX_PAD(0x03FC, 0x00B4, 2, 0x07B8, 2, 0),
>> + MX6_PAD_KEY_COL4__I2C3_SCL =
>> IOMUX_PAD(0x03FC, 0x00B4, IOMUX_CONFIG_SION | 2, 0x07B8, 2, 0),
>> MX6_PAD_KEY_COL4__USDHC2_LCTL =
>> IOMUX_PAD(0x03FC, 0x00B4, 3, 0x0000, 0, 0),
>> MX6_PAD_KEY_COL4__AUDMUX_AUD5_RXC =
>> IOMUX_PAD(0x03FC, 0x00B4, 4, 0x0664, 0, 0),
>> MX6_PAD_KEY_COL4__GPIO2_IO_14 =
>> IOMUX_PAD(0x03FC, 0x00B4, 5, 0x0000, 0, 0),
>> @@ -467,7 +467,7 @@ enum {
>>
>> MX6_PAD_KEY_ROW4__KPP_ROW_4 =
>> IOMUX_PAD(0x0410, 0x00C8, 0, 0x0000, 0, 0),
>> MX6_PAD_KEY_ROW4__ENET2_MDIO =
>> IOMUX_PAD(0x0410, 0x00C8, 1, 0x0770, 3, 0),
>> - MX6_PAD_KEY_ROW4__I2C3_SDA =
>> IOMUX_PAD(0x0410, 0x00C8, 2, 0x07BC, 2, 0),
>> + MX6_PAD_KEY_ROW4__I2C3_SDA =
>> IOMUX_PAD(0x0410, 0x00C8, IOMUX_CONFIG_SION | 2, 0x07BC, 2, 0),
>> MX6_PAD_KEY_ROW4__USDHC1_LCTL =
>> IOMUX_PAD(0x0410, 0x00C8, 3, 0x0000, 0, 0),
>> MX6_PAD_KEY_ROW4__AUDMUX_AUD5_RXFS =
>> IOMUX_PAD(0x0410, 0x00C8, 4, 0x0668, 0, 0),
>> MX6_PAD_KEY_ROW4__GPIO2_IO_19 =
>> IOMUX_PAD(0x0410, 0x00C8, 5, 0x0000, 0, 0),
>>
>
> Usually the SCL is output-only, driven by the I2C master. Why do you
> need to enable SION bit on SCL, if the pin will be used as output-only?
>
Right - I do not see why SION should be set.
Regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2015-01-29 17:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-12 8:46 [U-Boot] [PATCH 1/4] mx6sx: pins: Enable SION for I2C3 iomux setting Ye.Li
2015-01-12 8:46 ` [U-Boot] [PATCH 2/4] mx6: soc: Add ENET2 support Ye.Li
2015-02-10 10:22 ` Stefano Babic
2015-02-11 2:42 ` Li Ye-B37916
2015-02-11 12:46 ` Stefano Babic
2015-01-12 8:46 ` [U-Boot] [PATCH 3/4] mx6: clock: Modify GPMI clock to support mx6sx Ye.Li
2015-02-10 10:26 ` Stefano Babic
2015-02-11 3:14 ` Li Ye-B37916
2015-02-11 12:48 ` Stefano Babic
2015-01-12 8:46 ` [U-Boot] [PATCH 4/4] imx: mx6sxsabreauto: Add support for mx6sx SABREAUTO board Ye.Li
2015-02-10 10:51 ` Stefano Babic
2015-02-11 9:43 ` Li Ye-B37916
2015-02-11 13:21 ` Peng Fan
2015-01-12 10:37 ` [U-Boot] [PATCH 1/4] mx6sx: pins: Enable SION for I2C3 iomux setting Nikolay Dimitrov
2015-01-29 17:54 ` Stefano Babic [this message]
2015-02-09 13:27 ` Li Ye-B37916
2015-02-10 10:18 ` Stefano Babic
2015-02-15 15:11 ` Nikolay Dimitrov
2015-02-15 16:23 ` Stefano Babic
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=54CA73C9.4000806@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox