From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
Date: Wed, 17 Dec 2014 08:58:23 +0100 [thread overview]
Message-ID: <5491379F.3090607@i2se.com> (raw)
In-Reply-To: <CAOMZO5CQjpYtrNTT65-ikJua4N_osYj4UVgm3EV+sEvVWF59cg@mail.gmail.com>
Hi Fabio,
Am 17.12.2014 um 03:44 schrieb Fabio Estevam:
> Hi Stefan,
>
> On Sun, Dec 14, 2014 at 3:16 PM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>
>> Btw i hope this patch also fixes a SPI communication issue with our hardware
>> which forces us to bypass ref_io1 for ssp2.
> Does this patch fix the SPI issue?
unfortunately not. If the 3.19-rc1 has been released, i send the fixed
patch.
I've the theory that's an initialization issue. I've never heard of SPI
problems from the U-Boot users and we are using imx-bootlets.
I'll try to test it with U-Boot.
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Shawn Guo <shawn.guo@linaro.org>,
Mike Turquette <mturquette@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
Date: Wed, 17 Dec 2014 08:58:23 +0100 [thread overview]
Message-ID: <5491379F.3090607@i2se.com> (raw)
In-Reply-To: <CAOMZO5CQjpYtrNTT65-ikJua4N_osYj4UVgm3EV+sEvVWF59cg@mail.gmail.com>
Hi Fabio,
Am 17.12.2014 um 03:44 schrieb Fabio Estevam:
> Hi Stefan,
>
> On Sun, Dec 14, 2014 at 3:16 PM, Stefan Wahren <stefan.wahren@i2se.com> wrote:
>
>> Btw i hope this patch also fixes a SPI communication issue with our hardware
>> which forces us to bypass ref_io1 for ssp2.
> Does this patch fix the SPI issue?
unfortunately not. If the 3.19-rc1 has been released, i send the fixed
patch.
I've the theory that's an initialization issue. I've never heard of SPI
problems from the U-Boot users and we are using imx-bootlets.
I'll try to test it with U-Boot.
Stefan
next prev parent reply other threads:[~2014-12-17 7:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 15:28 [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers Stefan Wahren
2014-12-14 15:28 ` Stefan Wahren
2014-12-14 16:12 ` Marek Vasut
2014-12-14 16:12 ` Marek Vasut
2014-12-14 17:16 ` Stefan Wahren
2014-12-14 17:16 ` Stefan Wahren
2014-12-14 19:19 ` Marek Vasut
2014-12-14 19:19 ` Marek Vasut
2014-12-15 7:19 ` Stefan Wahren
2014-12-15 7:19 ` Stefan Wahren
2014-12-17 2:44 ` Fabio Estevam
2014-12-17 2:44 ` Fabio Estevam
2014-12-17 7:58 ` Stefan Wahren [this message]
2014-12-17 7:58 ` Stefan Wahren
2014-12-17 16:00 ` Marek Vasut
2014-12-17 16:00 ` Marek Vasut
2014-12-18 15:58 ` Stefan Wahren
2014-12-18 15:58 ` Stefan Wahren
2014-12-18 16:19 ` Marek Vasut
2014-12-18 16:19 ` Marek Vasut
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=5491379F.3090607@i2se.com \
--to=stefan.wahren@i2se.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.