From: Vladimir Zapolskiy <vz@mleia.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Matt Mackall <mpm@selenic.com>, Rob Herring <robh+dt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hwrng: mxc-rnga - add driver support on boards with device tree
Date: Tue, 6 Mar 2018 01:44:40 +0200 [thread overview]
Message-ID: <4e2a63d3-9011-24fb-15b7-d021748931ac@mleia.com> (raw)
In-Reply-To: <CAOMZO5DmtaAoZ5CEJDHjLSc4dwjHB4p1uO69-x8KNJ6bvvT7Dw@mail.gmail.com>
Hi Fabio,
On 03/06/2018 12:24 AM, Fabio Estevam wrote:
> Hi Vladimir,
>
> On Mon, Mar 5, 2018 at 7:21 PM, Vladimir Zapolskiy <vz@mleia.com> wrote:
>> The driver works well on i.MX31 powered boards with device description
>> taken from board device tree, the only change to add to the driver is
>> the missing OF device id, the affected list of included headers and
>> indentation in platform driver struct are beautified a little.
>
> Patch looks good.
>
you are welcome to ack :)
> I have an off-topic question though :-)
>
> Do you have mx31 device tree related patches so that you can test this?
Yes, I have a pretty good i.MX31 dtsi change (tested everything but USB
and multimedia, and that notorious watchdog problem still has to be
agreed with Uwe and solved), but I'm trying to save my time a little, and
my plan is to send everything altogether as a single imx31.dtsi update
(without instant pinctrl though). And basically RNGA support is the only
missing part at the moment.
> Do we have mx31 pinctrl support?
Yes, I have a complete and well tested i.MX31 pinctrl driver, it is done
similarly to all known Freescale pin controller drivers.
I sort of dislike it, and my preference is to "upgrade" it to utilize
generic pin multiplexing with groups, functions and pin configuration
as it is described in pinctrl-bindings.txt, then hopefully some ideas
or code can be migrated to support modern Freescale/NXP SoCs. Legacy
i.MX31 could serve as a distant and convenient test site in my opinion.
> Please advise.
>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2018-03-05 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 22:20 [PATCH v2 0/2] hwrng: mxc-rnga - add driver support on boards with device tree Vladimir Zapolskiy
2018-03-05 22:20 ` [PATCH v2 1/2] dt-bindings: rng: Document Freescale i.MX21 and i.MX31 RNGA compatibles Vladimir Zapolskiy
2018-03-05 23:53 ` Fabio Estevam
2018-03-05 22:21 ` [PATCH v2 2/2] hwrng: mxc-rnga - add driver support on boards with device tree Vladimir Zapolskiy
2018-03-05 22:24 ` Fabio Estevam
2018-03-05 23:44 ` Vladimir Zapolskiy [this message]
2018-03-05 23:58 ` Fabio Estevam
2018-03-05 23:54 ` Fabio Estevam
2018-03-07 16:13 ` Kim Phillips
2018-03-16 15:54 ` [PATCH v2 0/2] " 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=4e2a63d3-9011-24fb-15b7-d021748931ac@mleia.com \
--to=vz@mleia.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.org \
/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