| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 24 Jun 2014 20:47:52 -0500 From: Suman Anna <s-anna@...com> To: Tony Lindgren <tony@...mide.com> CC: Jassi Brar <jaswinder.singh@...aro.org>, Dave Gerlach <d-gerlach@...com>, <linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>, <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>, Suman Anna <s-anna@...com> Subject: [PATCH 0/6] OMAP Mailbox framework adoption & DT support Hi, The first 3 patches in this series adds the DT bindings and the DT-parse support to the OMAP mailbox driver. The last 3 patches make the changes to adopt to the v7 version of mailbox framework from Jassi Brar [1]. I have posted all the patches together since both touch the bindings and dictate the usage for the OMAP mailbox clients. The current OMAP mailbox clients - omap remoteproc and tidspbridge have also been converted to use the new api. The DT-support patches incorporates feedback from the last DT adoption series [2], with the following main changes: - Leverages more compatible strings - Dropped the properties "ti,mbox-num-users" and "ti,mbox-num-fifos"; with these values retrieved through driver match data and compatible strings - Dropped the properties "ti,mbox-names" and "ti,mbox-data" that were used to represent the sub-mailbox devices, which are now represented as child nodes of the respective mailbox controller device node. The series depends on the OMAP mailbox cleanup series [3] and the OMAP mailbox DT/hwmod cleanup series [4]. The following shows the boot/validation logs on various OMAP platforms: OMAP2 (SDP2430) : http://slexy.org/view/s20VHd3CIc OMAP3 (BeagleXM) : http://slexy.org/view/s204yxxE7Q OMAP4 (PandaBoard) : http://slexy.org/view/s20GDw9Lxq OMAP5 (OMAP5 uEVM) : http://slexy.org/view/s201gZlzSB DRA7 (DRA7 EVM) : http://slexy.org/view/s2CPnJ1Boz AM33xx (BeagleBone Black) : http://slexy.org/view/s20WvIuITK AM43xx (AM437x GP EVM) : http://slexy.org/view/s213DqnSg5 [1] https://lkml.org/lkml/2014/6/12/470 [2] http://marc.info/?l=linux-omap&m=137582560717973&w=2 [3] http://marc.info/?l=linux-omap&m=140365705821115&w=2 [4] http://marc.info/?l=linux-omap&m=140365833121612&w=2 Suman Anna (6): Documentation: dt: add omap mailbox bindings mailbox/omap: add support for parsing dt devices ARM: dts: OMAP2+: Add sub mailboxes device node information mailbox/omap: adapt to the new mailbox framework ARM: dts: OMAP2+: Add #mbox-cells property to all mailbox nodes mailbox/omap: add a custom of_xlate function .../devicetree/bindings/mailbox/omap-mailbox.txt | 104 ++++ arch/arm/boot/dts/am33xx.dtsi | 5 + arch/arm/boot/dts/am4372.dtsi | 5 + arch/arm/boot/dts/dra7.dtsi | 13 + arch/arm/boot/dts/omap2420.dtsi | 9 + arch/arm/boot/dts/omap2430.dtsi | 5 + arch/arm/boot/dts/omap3.dtsi | 5 + arch/arm/boot/dts/omap4.dtsi | 9 + arch/arm/boot/dts/omap5.dtsi | 9 + drivers/mailbox/omap-mailbox.c | 544 ++++++++++++++------- drivers/remoteproc/omap_remoteproc.c | 54 +- drivers/staging/tidspbridge/core/_tiomap.h | 3 +- drivers/staging/tidspbridge/core/io_sm.c | 7 +- drivers/staging/tidspbridge/core/tiomap3430.c | 22 +- drivers/staging/tidspbridge/core/tiomap_io.c | 7 +- .../tidspbridge/include/dspbridge/host_os.h | 1 + .../staging/tidspbridge/include/dspbridge/io_sm.h | 8 +- include/linux/omap-mailbox.h | 15 +- 18 files changed, 598 insertions(+), 227 deletions(-) create mode 100644 Documentation/devicetree/bindings/mailbox/omap-mailbox.txt -- 2.0.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists