linux-kernel - Re: [PATCH 3/6] atmel-mci: Optional controller reset before every command

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: <9f53b4330906171127y2fc7cc88w7764de9a6562e2a9@mail.gmail.com>
Date:	Wed, 17 Jun 2009 11:27:57 -0700
From:	Robert Emanuele <rob@...nuele.us>
To:	Marc Pignat <marc.pignat@...s.ch>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk, nicolas.ferre@...el.com,
	haavard.skinnemoen@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/6] atmel-mci: Optional controller reset before every 
	command

Marc,

(This may be a resend, gmail and its fancy text hates me.)

There has been debate over whether always reseting the MCI controller
is the correct thing to do.  I think for some platforms it is required
but there is no consensus to what those platforms are.  I think the
config option is the best of both worlds as a user of this
kernel/driver can choose to enable this or not without having to
modify their source.  It may even be a decent idea to enable this
option if they are using certain chips that we know reseting improves
their behavior.

Thank you,
Rob
--
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/