From: Matt Porter <mporter@konsulko.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Tony Lindgren" <tony@atomide.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Linux OMAP List" <linux-omap@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux ARM Kernel List" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: dts: am335x-boneblack: enable aes and sham
Date: Wed, 25 Feb 2015 13:42:52 -0500 [thread overview]
Message-ID: <20150225184252.GA27416@beef> (raw)
In-Reply-To: <CAOCHtYju0ZPV-BZS=L5S+JUX4gcRkJwqUZQBuURgGMo_Nmqt7g@mail.gmail.com>
On Wed, Feb 25, 2015 at 12:36:11PM -0600, Robert Nelson wrote:
> On Wed, Feb 25, 2015 at 11:07 AM, Matt Porter <mporter@konsulko.com> wrote:
> > Beaglebone Black doesn't have AES and SHAM enabled like the
> > original Beaglebone White dts. This breaks applications that
> > leverage the crypto blocks so fix this by enabling these nodes.
> >
> > Signed-off-by: Matt Porter <mporter@konsulko.com>
> > ---
> > arch/arm/boot/dts/am335x-boneblack.dts | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am335x-boneblack.dts b/arch/arm/boot/dts/am335x-boneblack.dts
> > index 5c42d25..00853ff 100644
> > --- a/arch/arm/boot/dts/am335x-boneblack.dts
> > +++ b/arch/arm/boot/dts/am335x-boneblack.dts
> > @@ -33,6 +33,14 @@
> > status = "okay";
> > };
> >
> > +&sham {
> > + status = "okay";
> > +};
> > +
> > +&aes {
> > + status = "okay";
> > +};
> > +
> > &am33xx_pinmux {
> > nxp_hdmi_bonelt_pins: nxp_hdmi_bonelt_pins {
> > pinctrl-single,pins = <
> > --
> > 1.8.4
>
> Shouldn't we just move these to: "am335x-bone-common.dtsi" ?
>
> (and then nuke the 6 lines in the am335x-bone.dts )
Good idea, v2 on the way.
-Matt
WARNING: multiple messages have this Message-ID (diff)
From: mporter@konsulko.com (Matt Porter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: am335x-boneblack: enable aes and sham
Date: Wed, 25 Feb 2015 13:42:52 -0500 [thread overview]
Message-ID: <20150225184252.GA27416@beef> (raw)
In-Reply-To: <CAOCHtYju0ZPV-BZS=L5S+JUX4gcRkJwqUZQBuURgGMo_Nmqt7g@mail.gmail.com>
On Wed, Feb 25, 2015 at 12:36:11PM -0600, Robert Nelson wrote:
> On Wed, Feb 25, 2015 at 11:07 AM, Matt Porter <mporter@konsulko.com> wrote:
> > Beaglebone Black doesn't have AES and SHAM enabled like the
> > original Beaglebone White dts. This breaks applications that
> > leverage the crypto blocks so fix this by enabling these nodes.
> >
> > Signed-off-by: Matt Porter <mporter@konsulko.com>
> > ---
> > arch/arm/boot/dts/am335x-boneblack.dts | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/am335x-boneblack.dts b/arch/arm/boot/dts/am335x-boneblack.dts
> > index 5c42d25..00853ff 100644
> > --- a/arch/arm/boot/dts/am335x-boneblack.dts
> > +++ b/arch/arm/boot/dts/am335x-boneblack.dts
> > @@ -33,6 +33,14 @@
> > status = "okay";
> > };
> >
> > +&sham {
> > + status = "okay";
> > +};
> > +
> > +&aes {
> > + status = "okay";
> > +};
> > +
> > &am33xx_pinmux {
> > nxp_hdmi_bonelt_pins: nxp_hdmi_bonelt_pins {
> > pinctrl-single,pins = <
> > --
> > 1.8.4
>
> Shouldn't we just move these to: "am335x-bone-common.dtsi" ?
>
> (and then nuke the 6 lines in the am335x-bone.dts )
Good idea, v2 on the way.
-Matt
next prev parent reply other threads:[~2015-02-25 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 17:07 [PATCH] ARM: dts: am335x-boneblack: enable aes and sham Matt Porter
2015-02-25 17:07 ` Matt Porter
2015-02-25 18:36 ` Robert Nelson
2015-02-25 18:36 ` Robert Nelson
2015-02-25 18:42 ` Matt Porter [this message]
2015-02-25 18:42 ` Matt Porter
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=20150225184252.GA27416@beef \
--to=mporter@konsulko.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robertcnelson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.