From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: mxc: allow executing the code that only applies to i.MX platforms
Date: Mon, 14 Dec 2015 18:37:23 +0800 [thread overview]
Message-ID: <566E9BE3.6040702@freescale.com> (raw)
In-Reply-To: <1450088599-23969-1-git-send-email-Qianyu.Gong@freescale.com>
On 12/14/2015 06:23 PM, Gong Qianyu wrote:
> The bus_i2c_init() is called before relocation and will assgin
> value to a static variable. If U-Boot is then still running in a
> flash device, it's theoretically not allowed to write data to flash
> without an erasing operation. For i.MX platforms, the U-Boot is
> always running in DDR.
>
> Actually it causes asynchronous error when the ARM64 system error report
> is enabled and the flash write protect is set.
>
> Signed-off-by: Gong Qianyu <Qianyu.Gong@freescale.com>
> ---
> drivers/i2c/mxc_i2c.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/i2c/mxc_i2c.c b/drivers/i2c/mxc_i2c.c
> index fa4c82f..4dddb83 100644
> --- a/drivers/i2c/mxc_i2c.c
> +++ b/drivers/i2c/mxc_i2c.c
> @@ -581,8 +581,11 @@ void bus_i2c_init(int index, int speed, int unused,
> return;
> }
>
> +#if defined(CONFIG_MX51) || defined(CONFIG_MX53) || \
> + defined(CONFIG_MX6) || defined(CONFIG_MX7)
> mxc_i2c_buses[index].idle_bus_fn = idle_bus_fn;
> mxc_i2c_buses[index].idle_bus_data = idle_bus_data;
> +#endif
>
I also think using variable mxc_i2c_buses is problematic. But using ifdef
doesn't look like a solution. I think this variable should be put into stack, or
use malloc. It works with execution-in-place in read-only space.
York
next prev parent reply other threads:[~2015-12-14 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 10:23 [U-Boot] [PATCH] i2c: mxc: allow executing the code that only applies to i.MX platforms Gong Qianyu
2015-12-14 10:37 ` York Sun [this message]
2015-12-14 11:03 ` Gong Q.Y.
2015-12-14 11:14 ` York Sun
2015-12-14 13:15 ` Gong Q.Y.
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=566E9BE3.6040702@freescale.com \
--to=yorksun@freescale.com \
--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