Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp4593016pxb; Tue, 22 Feb 2022 02:04:51 -0800 (PST) X-Google-Smtp-Source: ABdhPJwU0o4UodqmnvprOo81JGPDdz97rfdga2/pgjkqz0wgKMKB14ikfvej052gbnxvglqYiw+4 X-Received: by 2002:a17:902:da82:b0:14e:bbe8:35e6 with SMTP id j2-20020a170902da8200b0014ebbe835e6mr22303222plx.13.1645524291372; Tue, 22 Feb 2022 02:04:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645524291; cv=none; d=google.com; s=arc-20160816; b=A10+CtTlXUsRqbMhFGEacJcu903dSP8Ljyalz5reKvvR/y99gj6/6xgAGzQ0dqvQZ6 u8+7kpIiGEaOWXRV465bayUpZA326wcWadhJ/CEM8BJ8RRutWXCiET0zqSViBUXj48I2 41Bc6y2vwCNRwfX9FCE5TLNYYMs9eBKowfAAQn0TF3tYLfZf+Nib6IueIHdNc05TuAam LDNgYmvlfSo7PUNRcS0ZK7K3RZO0w4He/8ReDX7WcpqrDzJt6zlHlKSW/Im6m/d3tGgN T3Dl7g0WxU3pdv/Dx2pWBdHwcnvLvtFv3SmrxT1JU2bbBxDjgzDK0G/689PoAnbw5nXU VflA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=WlKysR3fh9cyTsBx7g4oItMVVN2tFxPCnNUbkhVb5nw=; b=dFPQBBxM/5UfaUaOHH2ltIqjlC4zmbIx2Yc9DrB80Zxst21+qFmVqowjaTlvdtJNo4 oB8TPlh6SVfOnjoHaH1pzFphkY/3xQz4GKIrjI16PexTC/BPj87c9+Bgdbx5KyEoaoYK I9w1RqZAy7QHI5zYUsT3usdOi/Kyrzms1+R9BzqCoJVU15Ad6jl7i9R8iy0QC4FbTNsP ltgDV8Id/Z/uF48YipFbyhIS0eBkA9jLVzqZdrnrRE+8aA5lhhO7B+eWKxLOUpgsWgfI B+chLkl8Ia5T1dUiG2e65687njZloNVIpkgxV/iQ8zU8CiasbH11TIbXXjsmAM5/y19k zYcQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NF0HYkUO; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id x2si5661670pgp.306.2022.02.22.02.04.27; Tue, 22 Feb 2022 02:04:51 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=NF0HYkUO; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230336AbiBVKCS (ORCPT + 99 others); Tue, 22 Feb 2022 05:02:18 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59712 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230320AbiBVKCP (ORCPT ); Tue, 22 Feb 2022 05:02:15 -0500 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 31CEC4D9E1; Tue, 22 Feb 2022 02:01:49 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id CB4E3B81979; Tue, 22 Feb 2022 10:01:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 748F6C340F1; Tue, 22 Feb 2022 10:01:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1645524106; bh=WlKysR3fh9cyTsBx7g4oItMVVN2tFxPCnNUbkhVb5nw=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=NF0HYkUOI0T/c3YEkbbhITM2wsz8a1nY+2BBS7Ae1Qq3VQlDKXDwweAiLgzY07a0D CkamuFzar7TxDgxm+QX7I/1Fq1DUFGwnXlPyDla0GiaEX32655LtgKJLcX4zJTFjls 61Il/UAGUO7DOVokjixgZgiqpmyhPo1jYvg7/pAGch63DfOdl2iFR/rng+VPpn2ELs xtC7Z1kwFlCUqvcnqxPJ9osES2woTYbxMPm+oOe4oBRJa2GDNGjQmvr70CX22+ay6d vDTZuWldYKrdJnsT7LE8zzB82pPUU2Dr/XdVS2sUIOGL4KiX3Iste78hkfDogmOIH0 zRPc6i0BqFc6A== Received: by mail-yb1-f178.google.com with SMTP id v186so39969219ybg.1; Tue, 22 Feb 2022 02:01:46 -0800 (PST) X-Gm-Message-State: AOAM533Zan2M52b4S0gar/jlnhE6g/l27hzEhWn7rRiAdM2DOCpyI3FT lPxte3sYTSsuCD51QJNxGp1zSUR9DasvpfhiaZ8= X-Received: by 2002:a25:4214:0:b0:624:6215:4823 with SMTP id p20-20020a254214000000b0062462154823mr13087478yba.432.1645524105607; Tue, 22 Feb 2022 02:01:45 -0800 (PST) MIME-Version: 1.0 References: <20220216113323.53332-1-Jason@zx2c4.com> <164543897830.26423.13654986323403498456.kvalo@kernel.org> In-Reply-To: <164543897830.26423.13654986323403498456.kvalo@kernel.org> From: Ard Biesheuvel Date: Tue, 22 Feb 2022 11:01:34 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3] ath9k: use hw_random API instead of directly dumping into random.c To: Kalle Valo Cc: "Jason A. Donenfeld" , miaoqing@codeaurora.org, Rui Salvaterra , =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , "Sepehrdad, Pouyan" , ath9k-devel , "linux-wireless@vger.kernel.org" , Dominik Brodowski , Linux Crypto Mailing List , Herbert Xu , LKML , Netdev , =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= , Florian Fainelli Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Mon, 21 Feb 2022 at 11:57, Kalle Valo wrote: > > "Jason A. Donenfeld" 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=C3=B8iland-J=C3=B8rgensen > > Cc: Kalle Valo > > Cc: Rui Salvaterra > > Cc: Dominik Brodowski > > Cc: Herbert Xu > > Signed-off-by: Jason A. Donenfeld > > Tested-by: Rui Salvaterra > > Acked-by: Toke H=C3=B8iland-J=C3=B8rgensen > > Signed-off-by: Kalle Valo > > Patch applied to ath-next branch of ath.git, thanks. > > fcd09c90c3c5 ath9k: use hw_random API instead of directly dumping into ra= ndom.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?