From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/3] I2C: mxc_i2c: make I2C1 and I2C2 optional
Date: Fri, 2 Oct 2015 10:43:22 +0200 [thread overview]
Message-ID: <560E43AA.9010604@denx.de> (raw)
In-Reply-To: <1442868219-5553-2-git-send-email-albert.aribaud@3adev.fr>
On 21/09/2015 22:43, Albert ARIBAUD (3ADEV) wrote:
> The driver assumed that I2C1 and I2C2 were always enabled,
> and if they were not, then an asynchronous abort was (silently)
> raised, to be caught much later on in the Linux kernel.
>
> Fix this by making I2C1 and I2C2 optional just like I2C3 and I2C4
> are.
>
> To make the change binary-invariant, declare I2C1 and I2C2 in
> every include/configs/ file which defines CONFIG_SYS_I2C_MXC.
>
> Also, while updating README about CONFIG_SYS_I2C_MXC_I2C1 and
> CONFIG_SYS_I2C_MXC_I2C2, add missing descriptions for I2C4 speed
> (CONFIG_SYS_MXC_I2C4_SPEED) and slave (CONFIG_SYS_MXC_I2C4_SLAVE)
> config options.
>
> Signed-off-by: Albert ARIBAUD (3ADEV) <albert.aribaud@3adev.fr>
> ---
Applied to u-boot-imx, thanks!
Best 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-10-02 8:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 20:43 [U-Boot] [PATCH v2 1/3] vf610: refactor DDRMC code Albert ARIBAUD
2015-09-21 20:43 ` [U-Boot] [PATCH v2 2/3] I2C: mxc_i2c: make I2C1 and I2C2 optional Albert ARIBAUD
2015-09-21 20:43 ` [U-Boot] [PATCH v2 3/3] vf610: add support for Phytec PCM052 Albert ARIBAUD
2015-10-02 8:43 ` Stefano Babic
2015-10-02 8:43 ` Stefano Babic [this message]
2015-10-02 8:38 ` [U-Boot] [PATCH v2 1/3] vf610: refactor DDRMC code 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=560E43AA.9010604@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