Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp359378imm; Tue, 19 Jun 2018 23:00:17 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIckFT9f6w6ztICL6TTzuTXTLedYYtUTAa67P4gcTY6m9oAmKdbrKJueDBaBdYSPk0kP8sS X-Received: by 2002:a17:902:8347:: with SMTP id z7-v6mr22545589pln.290.1529474417728; Tue, 19 Jun 2018 23:00:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529474417; cv=none; d=google.com; s=arc-20160816; b=SFl0gRYmCMhoGtNEBqS5Rac810Fe/Tj/ZGby39SeH36s6lm1h9EINASd+/AVbZKfd2 Gynme5DIf5RkbI/TYOJc1VCcaJ1NKSCHjO2gFZxxG5g4Pg5B7PRU8JNaR8nqrvZnH1DE KbINO7zwyqp638SN+EqjrfFmZebMDxXskDL1O8qIx6sqA8XLWtxTCoRN3S5XvYH76Slo kectnRK6NI3oE9yicKLo7d2FpZrto3ZG4j5HxsRcwCmsABBc3uE7ZXqVvEynodirR7y8 BBHOTNnB5VS7dgbiLKbLYv2GOn2E1GaJpbtrjBuhiOtnWC1lEk1//2gKlNCItNLagdr/ dWhA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:date:subject:user-agent:message-id :references:cc:in-reply-to:from:to:content-transfer-encoding :mime-version:dkim-signature:arc-authentication-results; bh=Bhx7L5vMC8fGosK/O1h3c5Sl9H4w69InS0mqL0AJ44k=; b=mi6dYynFEPsTv0NuIhKXd0Pekf+hp6o/y3WYSpISOkL0UOqgi8Xxz+6uQVsT0LRfFn CJg2dO5BjYaHTG0hQadDDwqxWZZ6dvTkru8M764rwPqYmLy7xUNV7Xp/yOqoIDbinwIM 60DiviLs1atpLYtHMvEoznkW1HQgzYBznto5SdLmFEQyzu+gVbYim2uf9ShUgAeaeC4M Jlc3t0rHloSRka1bpdVrCn1n2EtPwlLOjy5qYtDbZe79LBkFEruJb2S+aVjzSipx5rOm EHnCBzu798ZQrir6MMqbSwTPNGyyFqhpeJVU40uYNGY/URNGu+L3QeLcf0qxqesncbh7 GgpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=aolwsCt4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o6-v6si1373625pgs.216.2018.06.19.23.00.02; Tue, 19 Jun 2018 23:00:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=aolwsCt4; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753073AbeFTF6o (ORCPT + 99 others); Wed, 20 Jun 2018 01:58:44 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:37039 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751553AbeFTF6l (ORCPT ); Wed, 20 Jun 2018 01:58:41 -0400 Received: by mail-pf0-f196.google.com with SMTP id y5-v6so1040626pfn.4 for ; Tue, 19 Jun 2018 22:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:content-transfer-encoding:to:from:in-reply-to:cc :references:message-id:user-agent:subject:date; bh=Bhx7L5vMC8fGosK/O1h3c5Sl9H4w69InS0mqL0AJ44k=; b=aolwsCt49CBzqMXveACYT4R+ujFsavct5+UzfaoYbN1kZa0h8YeVl03uNhpTeK5dZi 9g67jxV/spaWKuiaeMr5c9+yBGQsgxBeIXd5ju/cSQnTgwA9DOWBQmLZ88Qp29it+40M mWvsKDA4tIUIdV81aUe5nVVb+jiC0Yne7oDoA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:content-transfer-encoding:to:from :in-reply-to:cc:references:message-id:user-agent:subject:date; bh=Bhx7L5vMC8fGosK/O1h3c5Sl9H4w69InS0mqL0AJ44k=; b=r9V3FUNoyYMDiwGY2WBQs2W1MPpnYVVUS3VkEPn4MqM07zm5ydQi3SLqHc3fOlf+L5 9leczNnmLuaC/iToC61v5m6muwjmQ+0hK3Vp0VCXkcCL1oB9MMEJ781Qu7at57eRMNU9 YJIHUYyWVXe6j/V21gyuieyQ19KD7x6TTmQl8Ifb4KJ3BMvPPMM38eji+0U+JKisOH2+ +LMbroPYbmaD+plwMPZEL66lKVNr4T+krpPxt5/k7ZnfJmL2XJc7zugG55x8FpVEdtdH S+Tr0hNN9nNwgg2/zdKqddTePhXej9FBI2XKCb9gaZMFlHVRU4D+/6qCBBK6TSHNiVp6 Wd0A== X-Gm-Message-State: APt69E0OGLMPYxEjc2/N8cvoTt3UqzFhuPp1XY3EdaANq6N6gAraat9M hRUrbCyyc9v+1YkacvSgI4WGLA== X-Received: by 2002:a63:2581:: with SMTP id l123-v6mr1114438pgl.226.1529474321074; Tue, 19 Jun 2018 22:58:41 -0700 (PDT) Received: from localhost ([2620:0:1000:1511:d30e:62c6:f82c:ff40]) by smtp.gmail.com with ESMTPSA id e68-v6sm2505326pfl.65.2018.06.19.22.58.40 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 19 Jun 2018 22:58:40 -0700 (PDT) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable To: Vinod Koul , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org From: Stephen Boyd In-Reply-To: <20180619095430.26358-3-vkoul@kernel.org> Cc: Matt Mackall , Herbert Xu , Arnd Bergmann , Greg Kroah-Hartman , linux-arm-msm@vger.kernel.org, vinod.koul@linaro.org, Vinod Koul References: <20180619095430.26358-1-vkoul@kernel.org> <20180619095430.26358-3-vkoul@kernel.org> Message-ID: <152947431955.16708.15247307054260887941@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: Re: [PATCH v2 2/2] hwrng: msm - Add support for prng v2 Date: Tue, 19 Jun 2018 22:58:39 -0700 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Vinod Koul (2018-06-19 02:54:30) > Qcom 8996 and later chips support prng v2 which requires to > implement only .read callback for hwrng. > = > This version of chip has multiple Execution Environments (EE) and > secure world is typically responsible for configuring the prng. Sometimes secure world is not configuring the rng though. I prefer we have a DT flag for this to indicate if secure world has configured it or not and then skip the init logic when the bool property is present in DT. Then the DT property can be set on firmwares that are making things blow up when we try to read the 'configured' register. I'd also file a bug to qcom to tell them to unlock that config register for reads so that things can work simpler, but who knows how that will work out. It really sounds like the hardware isn't actually different, just the firmware has decided to be more strict about making reads fail now.