[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9r4+ENUhZ6u26rAbq0iCWoKqTPYA7=_LWbGG98KvaCE6g@mail.gmail.com>
Date: Tue, 15 Feb 2022 16:38:53 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: miaoqing@...eaurora.org, Jason Cooper <jason@...edaemon.net>,
"Sepehrdad, Pouyan" <pouyans@....qualcomm.com>,
ath9k-devel <ath9k-devel@....qualcomm.com>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
Kalle Valo <kvalo@...nel.org>,
Toke Høiland-Jørgensen <toke@...hat.com>
Cc: Dominik Brodowski <linux@...inikbrodowski.net>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
LKML <linux-kernel@...r.kernel.org>,
Netdev <netdev@...r.kernel.org>
Subject: ath9k should perhaps use hw_random api?
Hi Ath9k Maintainers,
I'm emailing you because I've noticed that ath9k's rng.c is the *only*
driver in the whole of the tree that calls
add_hwgenerator_randomness() directly, rather than going through
Herbert's hw_random API, as every single other hardware RNG does.
I'm wondering if you'd consider converting your driver into something
suitable for the hw_random API (in drivers/char/hw_random/), rather
than adhoc rolling your own ath9k rng kthread. Is this something
you're actively maintaining and would be interested in doing?
Regards,
Jason
Powered by blists - more mailing lists