From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: "Scott Branden" <scott.branden@broadcom.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Rob Herring" <robh+dt@kernel.org>, "Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Alexandru Ardelean" <alexandru.ardelean@analog.com>,
"Neil Armstrong" <narmstrong@baylibre.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
"Rikard Falkeborn" <rikard.falkeborn@gmail.com>,
"Stefan Wahren" <stefan.wahren@i2se.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: rng: bcm2835: document reset support
Date: Tue, 23 Feb 2021 18:22:11 +0100 [thread overview]
Message-ID: <110b59a6-2359-89e1-5f20-7d2e1fd32a2f@gmail.com> (raw)
In-Reply-To: <23b28f9f-786d-8cdc-338f-efb4b23020a9@broadcom.com>
Hello Scott,
El 23/02/2021 a las 18:17, Scott Branden escribió:
> On 2021-02-23 8:36 a.m., Florian Fainelli wrote:
>>
>>
>> On 2/23/2021 8:01 AM, Álvaro Fernández Rojas wrote:
>>> Some devices may need to perform a reset before using the RNG, such as the
>>> BCM6368.
>>>
>>> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
>>
>> Since the reset is unique to the 6368, you may want to make the property
>> mandatory for the 6368 compatible string and optional otherwise.
>>
> Perhaps the reset could be done at an earlier boot stage as well and then the
> reset would even be optional on 6368?
>
No, this isn't possible on bmips, which is device tree only.
However, it's how is done in bcm63xx, which is why it wasn't needed before.
Best regards,
Álvaro.
next prev parent reply other threads:[~2021-02-23 17:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210222194510.14004-1-noltari@gmail.com>
2021-02-23 16:01 ` [PATCH 0/2] hwrng: bcm2835: add reset support Álvaro Fernández Rojas
2021-02-23 16:01 ` [PATCH 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-23 16:36 ` Florian Fainelli
2021-02-23 17:17 ` Scott Branden
2021-02-23 17:22 ` Álvaro Fernández Rojas [this message]
2021-02-23 16:01 ` [PATCH 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-02-24 8:22 ` [PATCH v4 0/2] " Álvaro Fernández Rojas
2021-02-24 8:22 ` [PATCH v4 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-24 8:22 ` [PATCH v4 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-03-03 13:52 ` Philipp Zabel
2021-03-03 14:06 ` Álvaro Fernández Rojas
2021-03-03 19:16 ` Florian Fainelli
2021-02-23 17:00 ` [PATCH v3 0/2] " Álvaro Fernández Rojas
2021-02-23 17:00 ` [PATCH v3 1/2] dt-bindings: rng: bcm2835: document " Álvaro Fernández Rojas
2021-02-23 19:34 ` Rob Herring
2021-02-23 20:48 ` Álvaro Fernández Rojas
2021-03-04 12:07 ` Nicolas Saenz Julienne
2021-03-04 12:18 ` Álvaro Fernández Rojas
2021-03-04 13:30 ` Nicolas Saenz Julienne
2021-03-04 14:57 ` Álvaro Fernández Rojas
2021-03-04 19:58 ` Rob Herring
2021-02-23 17:00 ` [PATCH v3 2/2] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-02-23 20:43 ` Florian Fainelli
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=110b59a6-2359-89e1-5f20-7d2e1fd32a2f@gmail.com \
--to=noltari@gmail.com \
--cc=alexandru.ardelean@analog.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mpm@selenic.com \
--cc=narmstrong@baylibre.com \
--cc=nfraprado@protonmail.com \
--cc=nsaenzjulienne@suse.de \
--cc=p.zabel@pengutronix.de \
--cc=rikard.falkeborn@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).