* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
@ 2014-12-14 15:28 Stefan Wahren
2014-12-14 16:12 ` Marek Vasut
0 siblings, 1 reply; 10+ messages in thread
From: Stefan Wahren @ 2014-12-14 15:28 UTC (permalink / raw)
To: linux-arm-kernel
According to i.MX23 and i.MX28 reference manual the fractional
clock control registers must be addressed by byte instructions.
This patch fixes the erroneous 32-bit access to these registers.
The changes has been tested only with a i.MX28 board, because i don't
have access to an i.MX23 board.
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
---
drivers/clk/mxs/clk-imx23.c | 8 +++++---
drivers/clk/mxs/clk-imx28.c | 14 ++++++++------
drivers/clk/mxs/clk-ref.c | 19 ++++++++++---------
3 files changed, 23 insertions(+), 18 deletions(-)
diff --git a/drivers/clk/mxs/clk-imx23.c b/drivers/clk/mxs/clk-imx23.c
index 9fc9359..371ba03 100644
--- a/drivers/clk/mxs/clk-imx23.c
+++ b/drivers/clk/mxs/clk-imx23.c
@@ -46,7 +46,8 @@ static void __iomem *digctrl;
#define BP_CLKSEQ_BYPASS_SAIF 0
#define BP_CLKSEQ_BYPASS_SSP 5
#define BP_SAIF_DIV_FRAC_EN 16
-#define BP_FRAC_IOFRAC 24
+
+#define FRAC_IO 3
static void __init clk_misc_init(void)
{
@@ -72,9 +73,10 @@ static void __init clk_misc_init(void)
/*
* 480 MHz seems too high to be ssp clock source directly,
* so set frac to get a 288 MHz ref_io.
+ * According to reference manual we must access frac bytewise.
*/
- writel_relaxed(0x3f << BP_FRAC_IOFRAC, FRAC + CLR);
- writel_relaxed(30 << BP_FRAC_IOFRAC, FRAC + SET);
+ writeb_relaxed(0x3f, FRAC + FRAC_IO + CLR);
+ writeb_relaxed(30, FRAC + FRAC_IO + SET);
}
static const char *sel_pll[] __initconst = { "pll", "ref_xtal", };
diff --git a/drivers/clk/mxs/clk-imx28.c b/drivers/clk/mxs/clk-imx28.c
index a6c3501..3eae119 100644
--- a/drivers/clk/mxs/clk-imx28.c
+++ b/drivers/clk/mxs/clk-imx28.c
@@ -53,8 +53,9 @@ static void __iomem *clkctrl;
#define BP_ENET_SLEEP 31
#define BP_CLKSEQ_BYPASS_SAIF0 0
#define BP_CLKSEQ_BYPASS_SSP0 3
-#define BP_FRAC0_IO1FRAC 16
-#define BP_FRAC0_IO0FRAC 24
+
+#define FRAC0_IO1 2
+#define FRAC0_IO0 3
static void __iomem *digctrl;
#define DIGCTRL digctrl
@@ -118,11 +119,12 @@ static void __init clk_misc_init(void)
/*
* 480 MHz seems too high to be ssp clock source directly,
* so set frac0 to get a 288 MHz ref_io0 and ref_io1.
+ * According to reference manual we must access frac0 bytewise.
*/
- val = readl_relaxed(FRAC0);
- val &= ~((0x3f << BP_FRAC0_IO0FRAC) | (0x3f << BP_FRAC0_IO1FRAC));
- val |= (30 << BP_FRAC0_IO0FRAC) | (30 << BP_FRAC0_IO1FRAC);
- writel_relaxed(val, FRAC0);
+ writeb_relaxed(0x3f, FRAC0 + FRAC0_IO0 + CLR);
+ writeb_relaxed(30, FRAC0 + FRAC0_IO0 + SET);
+ writeb_relaxed(0x3f, FRAC0 + FRAC0_IO1 + CLR);
+ writeb_relaxed(30, FRAC0 + FRAC0_IO1 + SET);
}
static const char *sel_cpu[] __initconst = { "ref_cpu", "ref_xtal", };
diff --git a/drivers/clk/mxs/clk-ref.c b/drivers/clk/mxs/clk-ref.c
index 4adeed6..ad3851c 100644
--- a/drivers/clk/mxs/clk-ref.c
+++ b/drivers/clk/mxs/clk-ref.c
@@ -16,6 +16,8 @@
#include <linux/slab.h>
#include "clk.h"
+#define BF_CLKGATE BIT(7)
+
/**
* struct clk_ref - mxs reference clock
* @hw: clk_hw for the reference clock
@@ -39,7 +41,7 @@ static int clk_ref_enable(struct clk_hw *hw)
{
struct clk_ref *ref = to_clk_ref(hw);
- writel_relaxed(1 << ((ref->idx + 1) * 8 - 1), ref->reg + CLR);
+ writeb_relaxed(BF_CLKGATE, ref->reg + ref->idx + CLR);
return 0;
}
@@ -48,7 +50,7 @@ static void clk_ref_disable(struct clk_hw *hw)
{
struct clk_ref *ref = to_clk_ref(hw);
- writel_relaxed(1 << ((ref->idx + 1) * 8 - 1), ref->reg + SET);
+ writeb_relaxed(BF_CLKGATE, ref->reg + ref->idx + SET);
}
static unsigned long clk_ref_recalc_rate(struct clk_hw *hw,
@@ -56,7 +58,7 @@ static unsigned long clk_ref_recalc_rate(struct clk_hw *hw,
{
struct clk_ref *ref = to_clk_ref(hw);
u64 tmp = parent_rate;
- u8 frac = (readl_relaxed(ref->reg) >> (ref->idx * 8)) & 0x3f;
+ u8 frac = readb_relaxed(ref->reg + ref->idx) & 0x3f;
tmp *= 18;
do_div(tmp, frac);
@@ -93,8 +95,7 @@ static int clk_ref_set_rate(struct clk_hw *hw, unsigned long rate,
struct clk_ref *ref = to_clk_ref(hw);
unsigned long flags;
u64 tmp = parent_rate;
- u32 val;
- u8 frac, shift = ref->idx * 8;
+ u8 frac, val;
tmp = tmp * 18 + rate / 2;
do_div(tmp, rate);
@@ -107,10 +108,10 @@ static int clk_ref_set_rate(struct clk_hw *hw, unsigned long rate,
spin_lock_irqsave(&mxs_lock, flags);
- val = readl_relaxed(ref->reg);
- val &= ~(0x3f << shift);
- val |= frac << shift;
- writel_relaxed(val, ref->reg);
+ val = readb_relaxed(ref->reg + ref->idx);
+ val &= ~0x3f;
+ val |= frac;
+ writeb_relaxed(val, ref->reg + ref->idx);
spin_unlock_irqrestore(&mxs_lock, flags);
--
1.7.9.5
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-14 15:28 [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers Stefan Wahren
@ 2014-12-14 16:12 ` Marek Vasut
2014-12-14 17:16 ` Stefan Wahren
0 siblings, 1 reply; 10+ messages in thread
From: Marek Vasut @ 2014-12-14 16:12 UTC (permalink / raw)
To: linux-arm-kernel
On Sunday, December 14, 2014 at 04:28:53 PM, Stefan Wahren wrote:
> According to i.MX23 and i.MX28 reference manual the fractional
> clock control registers must be addressed by byte instructions.
>
> This patch fixes the erroneous 32-bit access to these registers.
>
> The changes has been tested only with a i.MX28 board, because i don't
> have access to an i.MX23 board.
The clock block is the same, so this _should_ be fine.
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
> drivers/clk/mxs/clk-imx23.c | 8 +++++---
> drivers/clk/mxs/clk-imx28.c | 14 ++++++++------
> drivers/clk/mxs/clk-ref.c | 19 ++++++++++---------
> 3 files changed, 23 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/clk/mxs/clk-imx23.c b/drivers/clk/mxs/clk-imx23.c
> index 9fc9359..371ba03 100644
> --- a/drivers/clk/mxs/clk-imx23.c
> +++ b/drivers/clk/mxs/clk-imx23.c
> @@ -46,7 +46,8 @@ static void __iomem *digctrl;
> #define BP_CLKSEQ_BYPASS_SAIF 0
> #define BP_CLKSEQ_BYPASS_SSP 5
> #define BP_SAIF_DIV_FRAC_EN 16
> -#define BP_FRAC_IOFRAC 24
> +
> +#define FRAC_IO 3
>
> static void __init clk_misc_init(void)
> {
> @@ -72,9 +73,10 @@ static void __init clk_misc_init(void)
> /*
> * 480 MHz seems too high to be ssp clock source directly,
> * so set frac to get a 288 MHz ref_io.
> + * According to reference manual we must access frac bytewise.
> */
> - writel_relaxed(0x3f << BP_FRAC_IOFRAC, FRAC + CLR);
> - writel_relaxed(30 << BP_FRAC_IOFRAC, FRAC + SET);
> + writeb_relaxed(0x3f, FRAC + FRAC_IO + CLR);
> + writeb_relaxed(30, FRAC + FRAC_IO + SET);
> }
>
> static const char *sel_pll[] __initconst = { "pll", "ref_xtal", };
> diff --git a/drivers/clk/mxs/clk-imx28.c b/drivers/clk/mxs/clk-imx28.c
> index a6c3501..3eae119 100644
> --- a/drivers/clk/mxs/clk-imx28.c
> +++ b/drivers/clk/mxs/clk-imx28.c
> @@ -53,8 +53,9 @@ static void __iomem *clkctrl;
> #define BP_ENET_SLEEP 31
> #define BP_CLKSEQ_BYPASS_SAIF0 0
> #define BP_CLKSEQ_BYPASS_SSP0 3
> -#define BP_FRAC0_IO1FRAC 16
> -#define BP_FRAC0_IO0FRAC 24
> +
> +#define FRAC0_IO1 2
> +#define FRAC0_IO0 3
>
> static void __iomem *digctrl;
> #define DIGCTRL digctrl
> @@ -118,11 +119,12 @@ static void __init clk_misc_init(void)
> /*
> * 480 MHz seems too high to be ssp clock source directly,
> * so set frac0 to get a 288 MHz ref_io0 and ref_io1.
> + * According to reference manual we must access frac0 bytewise.
> */
> - val = readl_relaxed(FRAC0);
> - val &= ~((0x3f << BP_FRAC0_IO0FRAC) | (0x3f << BP_FRAC0_IO1FRAC));
> - val |= (30 << BP_FRAC0_IO0FRAC) | (30 << BP_FRAC0_IO1FRAC);
> - writel_relaxed(val, FRAC0);
> + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO0 + CLR);
> + writeb_relaxed(30, FRAC0 + FRAC0_IO0 + SET);
> + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO1 + CLR);
> + writeb_relaxed(30, FRAC0 + FRAC0_IO1 + SET);
This used to be a R-M-W sequence, but now it's changed to multiple writes. This
changes the behavior and seeing you use the CLR register, I am worried this
might be prone to clock glitches. What do you think please ?
[...]
Also, it might be a good idea to zap the 0x3f mask and use HEX and DEC numbers
consistently, but this is an idea for another patch.
Best regards,
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-14 16:12 ` Marek Vasut
@ 2014-12-14 17:16 ` Stefan Wahren
2014-12-14 19:19 ` Marek Vasut
2014-12-17 2:44 ` Fabio Estevam
0 siblings, 2 replies; 10+ messages in thread
From: Stefan Wahren @ 2014-12-14 17:16 UTC (permalink / raw)
To: linux-arm-kernel
Hi Marek,
> Marek Vasut <marex@denx.de> hat am 14. Dezember 2014 um 17:12 geschrieben:
>
> >
> > static void __iomem *digctrl;
> > #define DIGCTRL digctrl
> > @@ -118,11 +119,12 @@ static void __init clk_misc_init(void)
> > /*
> > * 480 MHz seems too high to be ssp clock source directly,
> > * so set frac0 to get a 288 MHz ref_io0 and ref_io1.
> > + * According to reference manual we must access frac0 bytewise.
> > */
> > - val = readl_relaxed(FRAC0);
> > - val &= ~((0x3f << BP_FRAC0_IO0FRAC) | (0x3f << BP_FRAC0_IO1FRAC));
> > - val |= (30 << BP_FRAC0_IO0FRAC) | (30 << BP_FRAC0_IO1FRAC);
> > - writel_relaxed(val, FRAC0);
> > + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO0 + CLR);
> > + writeb_relaxed(30, FRAC0 + FRAC0_IO0 + SET);
> > + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO1 + CLR);
> > + writeb_relaxed(30, FRAC0 + FRAC0_IO1 + SET);
>
> This used to be a R-M-W sequence, but now it's changed to multiple writes.
> This
> changes the behavior and seeing you use the CLR register, I am worried this
> might be prone to clock glitches. What do you think please ?
you are right. I adapt the imx23 init to the imx28 to make code simple. But it
would be better to avoid glitches.
I hope it's okay for this bugfix to introduce a R-M-W sequence for the imx23
init. So it's consequent.
>
> [...]
>
> Also, it might be a good idea to zap the 0x3f mask and use HEX and DEC numbers
> consistently, but this is an idea for another patch.
Yes.
Btw i hope this patch also fixes a SPI communication issue with our hardware
which forces us to bypass ref_io1 for ssp2.
But i will have access to that hardware tomorrow.
Thanks
Stefan
>
> Best regards,
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-14 17:16 ` Stefan Wahren
@ 2014-12-14 19:19 ` Marek Vasut
2014-12-15 7:19 ` Stefan Wahren
2014-12-17 2:44 ` Fabio Estevam
1 sibling, 1 reply; 10+ messages in thread
From: Marek Vasut @ 2014-12-14 19:19 UTC (permalink / raw)
To: linux-arm-kernel
On Sunday, December 14, 2014 at 06:16:17 PM, Stefan Wahren wrote:
> Hi Marek,
>
> > Marek Vasut <marex@denx.de> hat am 14. Dezember 2014 um 17:12 geschrieben:
> > > static void __iomem *digctrl;
> > > #define DIGCTRL digctrl
> > > @@ -118,11 +119,12 @@ static void __init clk_misc_init(void)
> > > /*
> > > * 480 MHz seems too high to be ssp clock source directly,
> > > * so set frac0 to get a 288 MHz ref_io0 and ref_io1.
> > > + * According to reference manual we must access frac0 bytewise.
> > > */
> > > - val = readl_relaxed(FRAC0);
> > > - val &= ~((0x3f << BP_FRAC0_IO0FRAC) | (0x3f << BP_FRAC0_IO1FRAC));
> > > - val |= (30 << BP_FRAC0_IO0FRAC) | (30 << BP_FRAC0_IO1FRAC);
> > > - writel_relaxed(val, FRAC0);
> > > + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO0 + CLR);
> > > + writeb_relaxed(30, FRAC0 + FRAC0_IO0 + SET);
> > > + writeb_relaxed(0x3f, FRAC0 + FRAC0_IO1 + CLR);
> > > + writeb_relaxed(30, FRAC0 + FRAC0_IO1 + SET);
> >
> > This used to be a R-M-W sequence, but now it's changed to multiple
> > writes. This
> > changes the behavior and seeing you use the CLR register, I am worried
> > this might be prone to clock glitches. What do you think please ?
>
> you are right. I adapt the imx23 init to the imx28 to make code simple. But
> it would be better to avoid glitches.
> I hope it's okay for this bugfix to introduce a R-M-W sequence for the
> imx23 init. So it's consequent.
It should be OK. Make sure to document it in the commit message.
> > [...]
> >
> > Also, it might be a good idea to zap the 0x3f mask and use HEX and DEC
> > numbers consistently, but this is an idea for another patch.
>
> Yes.
>
> Btw i hope this patch also fixes a SPI communication issue with our
> hardware which forces us to bypass ref_io1 for ssp2.
> But i will have access to that hardware tomorrow.
Which issue would that be please ? What are the symptoms ?
Best regards,
Marek Vasut
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-14 19:19 ` Marek Vasut
@ 2014-12-15 7:19 ` Stefan Wahren
0 siblings, 0 replies; 10+ messages in thread
From: Stefan Wahren @ 2014-12-15 7:19 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
Am 14.12.2014 um 20:19 schrieb Marek Vasut:
> On Sunday, December 14, 2014 at 06:16:17 PM, Stefan Wahren wrote:
>>> [...]
>>>
>>> Also, it might be a good idea to zap the 0x3f mask and use HEX and DEC
>>> numbers consistently, but this is an idea for another patch.
>> Yes.
>>
>> Btw i hope this patch also fixes a SPI communication issue with our
>> hardware which forces us to bypass ref_io1 for ssp2.
>> But i will have access to that hardware tomorrow.
> Which issue would that be please ?
i've posted the issue in the Freescale Community [1].
> What are the symptoms ?
Bits from the SPI slave are misinterpreted.
BR Stefan
[1] - https://community.freescale.com/thread/310434
>
> Best regards,
> Marek Vasut
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-14 17:16 ` Stefan Wahren
2014-12-14 19:19 ` Marek Vasut
@ 2014-12-17 2:44 ` Fabio Estevam
2014-12-17 7:58 ` Stefan Wahren
1 sibling, 1 reply; 10+ messages in thread
From: Fabio Estevam @ 2014-12-17 2:44 UTC (permalink / raw)
To: linux-arm-kernel
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?
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-17 2:44 ` Fabio Estevam
@ 2014-12-17 7:58 ` Stefan Wahren
2014-12-17 16:00 ` Marek Vasut
0 siblings, 1 reply; 10+ messages in thread
From: Stefan Wahren @ 2014-12-17 7:58 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-17 7:58 ` Stefan Wahren
@ 2014-12-17 16:00 ` Marek Vasut
2014-12-18 15:58 ` Stefan Wahren
0 siblings, 1 reply; 10+ messages in thread
From: Marek Vasut @ 2014-12-17 16:00 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-17 16:00 ` Marek Vasut
@ 2014-12-18 15:58 ` Stefan Wahren
2014-12-18 16:19 ` Marek Vasut
0 siblings, 1 reply; 10+ messages in thread
From: Stefan Wahren @ 2014-12-18 15:58 UTC (permalink / raw)
To: linux-arm-kernel
Hi Marek,
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.
Stefan
^ permalink raw reply [flat|nested] 10+ messages in thread
* [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers
2014-12-18 15:58 ` Stefan Wahren
@ 2014-12-18 16:19 ` Marek Vasut
0 siblings, 0 replies; 10+ messages in thread
From: Marek Vasut @ 2014-12-18 16:19 UTC (permalink / raw)
To: linux-arm-kernel
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
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2014-12-18 16:19 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-14 15:28 [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers Stefan Wahren
2014-12-14 16:12 ` Marek Vasut
2014-12-14 17:16 ` Stefan Wahren
2014-12-14 19:19 ` Marek Vasut
2014-12-15 7:19 ` Stefan Wahren
2014-12-17 2:44 ` Fabio Estevam
2014-12-17 7:58 ` Stefan Wahren
2014-12-17 16:00 ` Marek Vasut
2014-12-18 15:58 ` Stefan Wahren
2014-12-18 16:19 ` Marek Vasut
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).