linux-kernel - Re: [PATCH] ARM: pxa: fix DFI bus lockups on startup

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] [day] [month] [year] [list]

Message-ID: <874mizu6gx.fsf@belgarion.home>
Date:	Sat, 12 Sep 2015 15:12:30 +0200
From:	Robert Jarzmik <robert.jarzmik@...e.fr>
To:	Daniel Mack <daniel@...que.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ARM: pxa: fix DFI bus lockups on startup

Robert Jarzmik <robert.jarzmik@...e.fr> writes:

> After the conversion of pxa architecture to common clock framework, the
> NAND clock can be disabled on startup if no nand driver claims it.
>
> In this case, it happens that if the bootloader used the NAND and set
> the DFI arbitration bit, the next access to a static memory controller
> area, such as an ethernet card, the system bus will stall, and the core
> will be stalled forever.
>
> Fix this by clearing the DFI arbritration bit in pxa3xx startup. The bit
> will be enabled the pxa3xx-nand driver on need anyway. The only left
> requirement is that upon pxa3xx-nand removal, the bit should be cleared
> before the clock is disabled.
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@...e.fr>
Queued to pxa/fixes.

-- 
Robert
--
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/