Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753389AbbBYSgO (ORCPT ); Wed, 25 Feb 2015 13:36:14 -0500 Received: from mail-ie0-f182.google.com ([209.85.223.182]:33560 "EHLO mail-ie0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752752AbbBYSgM (ORCPT ); Wed, 25 Feb 2015 13:36:12 -0500 MIME-Version: 1.0 In-Reply-To: <1424884070-25891-1-git-send-email-mporter@konsulko.com> References: <1424884070-25891-1-git-send-email-mporter@konsulko.com> Date: Wed, 25 Feb 2015 12:36:11 -0600 Message-ID: Subject: Re: [PATCH] ARM: dts: am335x-boneblack: enable aes and sham From: Robert Nelson To: Matt Porter Cc: =?UTF-8?Q?Beno=C3=AEt_Cousson?= , Tony Lindgren , Mark Rutland , Linux OMAP List , Rob Herring , Linux Kernel Mailing List , Linux ARM Kernel List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1333 Lines: 46 On Wed, Feb 25, 2015 at 11:07 AM, Matt Porter 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 > --- > 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 ) Regards, -- Robert Nelson http://www.rcn-ee.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/