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
| ||
|
Message-ID: <20171228164944.crphv46zegvwautk@localhost> Date: Thu, 28 Dec 2017 08:49:44 -0800 From: Richard Cochran <richardcochran@...il.com> To: Sagar Arun Kamble <sagar.a.kamble@...el.com> Cc: Takashi Iwai <tiwai@...e.de>, linux-kernel@...r.kernel.org, alsa-devel@...a-project.org, Vinod Koul <vinod.koul@...el.com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [alsa-devel] [PATCH 15/27] ALSA: hda - Use timecounter_initialize interface On Tue, Dec 26, 2017 at 01:07:35PM +0530, Sagar Arun Kamble wrote: > > Or can we provide simpler versions for covering some defaults? At > > least reducing the number of arguments would make things easier. > Thought about specifying 1. cyclecounter read func 2. frequency 3. width of > counter as parameters here > which can get rid of mult, shift params. But this is not easy as most of the > drivers do not specify > cyclecounter frequency and instead hard-code the mult/shift factors. You are talking about using clocks_calc_mult_shift() here, right? (See the usage example in drivers/net/ethernet/ti/cpts.c). This is a good idea, and it is worth getting the driver authors' input to figure out the correct parameters. I bet we can use that almost everywhere. If there are any drivers that cannot be converted, then we can leave some sort of low level legacy initialization method. Thanks, Richard
Powered by blists - more mailing lists