linux-kernel - Re: Re: Fwd: [PATCH] [MMC] fix clock problem in PXA255/270

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 for Android: free password hash cracker in your pocket

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

Message-ID: <60c632a5.15d4db9c.4816f8d4.b398b@o2.pl>
Date:	Tue, 29 Apr 2008 12:30:44 +0200
From:	Tadeusz Gozdek <linux_fan@...pl>
To:	 Pierre  Ossman <drzeus-list@...eus.cx>
Cc:	linux-kernel@...r.kernel.org, marcel@...tmann.org
Subject: Re: Re: Fwd: [PATCH] [MMC] fix clock problem in PXA255/270

OK probably I didn't understand your policy. I ever thought that the host controller should know, when the clock should be off.
The PXA controller is different and it was the simples (but effective) way to solve this difference.

So, I hope it will be usable for people which has problem with "always on" clock, until you solve it in different way (if you going to do this).

Thanks 
Tadeusz

> That is a policy with possible side-effects (i.e. needs to be
> configurable), and host independent so it should be in the core. So I'm
> afraid I have to NAK your patch.
> 
> As a side-note, the PXA driver shouldn't be fiddling with the clock the
> way it does right now in the first place, but I have no maintainer to
> yell at. Patches removing that behaviour are very welcome.

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