mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <quic_bjorande@quicinc.com>
To: Brian Masney <bmasney@redhat.com>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<quic_omprsing@quicinc.com>, <neil.armstrong@linaro.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <ernesto.mnd.fernandez@gmail.com>,
	<quic_jhugo@quicinc.com>
Subject: Re: [PATCH v3 0/2] crypto: qcom-rng: fix support for ACPI-based systems
Date: Thu, 5 Sep 2024 19:04:56 -0700	[thread overview]
Message-ID: <ZtpjSPI5+loYoT2M@hu-bjorande-lv.qualcomm.com> (raw)
In-Reply-To: <20240906002521.1163311-1-bmasney@redhat.com>

On Thu, Sep 05, 2024 at 08:25:19PM -0400, Brian Masney wrote:
> The qcom-rng driver supports both ACPI and device tree based systems.
> ACPI support was broken when the hw_random interface support was added.
> This small series gets that working again.
> 
> This fix was boot tested on a Qualcomm Amberwing server (ACPI based) and
> on a Qualcomm SA8775p Automotive Development Board (DT based). I also
> verified that qcom-rng shows up in /proc/crypto on both systems.
> 

Reviewed-by: Bjorn Andersson <quic_bjorande@quicinc.com>

Regards,
Bjorn

> Changes since v2:
> - Simplify ACPI fix based on what's done with other drivers (Brian)
> 
> Changes since v1:
> - Use qcom_prng_ee_match_data instead of qcom_prng_match_data for the
>   true skip_init to match previous behavior (Ernesto)
> - Reordered patches so fix is first (Dmitry)
> 
> Brian Masney (2):
>   crypto: qcom-rng: fix support for ACPI-based systems
>   crypto: qcom-rng: rename *_of_data to *_match_data
> 
>  drivers/crypto/qcom-rng.c | 24 ++++++++++++------------
>  1 file changed, 12 insertions(+), 12 deletions(-)
> 
> -- 
> 2.46.0
> 

  parent reply	other threads:[~2024-09-06  2:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06  0:25 Brian Masney
2024-09-06  0:25 ` [PATCH v3 1/2] " Brian Masney
2024-09-06  0:44   ` Dmitry Baryshkov
2024-09-06  0:25 ` [PATCH v3 2/2] crypto: qcom-rng: rename *_of_data to *_match_data Brian Masney
2024-09-06  0:52   ` Dmitry Baryshkov
2024-09-06  2:04 ` Bjorn Andersson [this message]
2024-09-13 10:31 ` [PATCH v3 0/2] crypto: qcom-rng: fix support for ACPI-based systems Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZtpjSPI5+loYoT2M@hu-bjorande-lv.qualcomm.com \
    --to=quic_bjorande@quicinc.com \
    --cc=bmasney@redhat.com \
    --cc=davem@davemloft.net \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=quic_omprsing@quicinc.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®