From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
Date: Thu, 18 Dec 2014 17:19:34 +0100 [thread overview]
Message-ID: <201412181719.34334.marex@denx.de> (raw)
In-Reply-To: <5492F9A4.3070805@i2se.com>
On Thursday, December 18, 2014 at 04:58:28 PM, Stefan Wahren wrote:
> Hi Marek,
Hello Stefan,
> Am 17.12.2014 um 17:00 schrieb Marek Vasut:
> > On Wednesday, December 17, 2014 at 08:58:23 AM, Stefan Wahren wrote:
> >> 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.
> >
> > Please keep me in the loop, I'd be interested in what you find. Thanks!
> >
> > Best regards,
> > Marek Vasut
>
> i tested it with U-Boot, but the issue still exists. If there is any
> progress, i'll inform you.
Thanks!
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Fabio Estevam <festevam@gmail.com>,
"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: Thu, 18 Dec 2014 17:19:34 +0100 [thread overview]
Message-ID: <201412181719.34334.marex@denx.de> (raw)
In-Reply-To: <5492F9A4.3070805@i2se.com>
On Thursday, December 18, 2014 at 04:58:28 PM, Stefan Wahren wrote:
> Hi Marek,
Hello Stefan,
> Am 17.12.2014 um 17:00 schrieb Marek Vasut:
> > On Wednesday, December 17, 2014 at 08:58:23 AM, Stefan Wahren wrote:
> >> 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.
> >
> > Please keep me in the loop, I'd be interested in what you find. Thanks!
> >
> > Best regards,
> > Marek Vasut
>
> i tested it with U-Boot, but the issue still exists. If there is any
> progress, i'll inform you.
Thanks!
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-12-18 16:19 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
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 [this message]
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=201412181719.34334.marex@denx.de \
--to=marex@denx.de \
--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.