On Mon, 21 Feb 2022 at 11:57, Kalle Valo <kvalo@xxxxxxxxxx> wrote: > > "Jason A. Donenfeld" <Jason@xxxxxxxxx> wrote: > > > Hardware random number generators are supposed to use the hw_random > > framework. This commit turns ath9k's kthread-based design into a proper > > hw_random driver. > > > > Cc: Toke Høiland-Jørgensen <toke@xxxxxxxxxx> > > Cc: Kalle Valo <kvalo@xxxxxxxxxx> > > Cc: Rui Salvaterra <rsalvaterra@xxxxxxxxx> > > Cc: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx> > > Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> > > Signed-off-by: Jason A. Donenfeld <Jason@xxxxxxxxx> > > Tested-by: Rui Salvaterra <rsalvaterra@xxxxxxxxx> > > Acked-by: Toke Høiland-Jørgensen <toke@xxxxxxx> > > Signed-off-by: Kalle Valo <quic_kvalo@xxxxxxxxxxx> > > Patch applied to ath-next branch of ath.git, thanks. > > fcd09c90c3c5 ath9k: use hw_random API instead of directly dumping into random.c > With this patch, it seems we end up registering the hw_rng every time the link goes up, and unregister it again when the link goes down, right? Wouldn't it be better to split off this driver from the 802.11 link state handling?
