linux-kernel - Re: [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5492F9A4.3070805@i2se.com>
Date:	Thu, 18 Dec 2014 16:58:28 +0100
From:	Stefan Wahren <stefan.wahren@...e.com>
To:	Marek Vasut <marex@...x.de>
CC:	Fabio Estevam <festevam@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Shawn Guo <shawn.guo@...aro.org>,
	Mike Turquette <mturquette@...aro.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH RFC] clk: mxs: Fix invalid 32-bit access to frac registers

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@...e.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/