On Aug 8, 2013, at 8:30 AM, Lothar Waßmann wrote: > This patch series does the following: > > - let the driver be "disabled" by default in imx28.dtsi > - coding style cleanups in drivers/crypto/dcp.c > - use the "official" 'fsl,' prefix in the 'compatible' property > > The last patch adds a new entry to the of_match_table of the driver, > so that current DT blobs will still work. When out of tree users > (mentioned in the commit log of 519d8b1a "Added support for > Freescale's DCP co-processor") have updated their DTBs the old entry > 'fsl-dsp' can be removed from the driver. > > This patch series requires at least > "[PATCH 2/8] ARM: dts: mxs: add labels to most nodes for easier reference" > from the patch series: > <1375966287-6784-1-git-send-email-LW@xxxxxxxxxxxxxxxxxxx> to be > applied. > > arch/arm/boot/dts/imx28.dtsi | 2 +- > b/arch/arm/boot/dts/imx28-evk.dts | 4 ++++ > b/arch/arm/boot/dts/imx28.dtsi | 3 ++- > b/drivers/crypto/dcp.c | 11 +++++------ > drivers/crypto/dcp.c | 2 ++ > 5 files changed, 14 insertions(+), 8 deletions(-) > > -- > To unsubscribe from this list: send the line "unsubscribe devicetree" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html Is there an actual binding spec for fsl,dcp? If not, there really should be. - k -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
