Re: [PATCHv2 0/5] OMAP Mailbox framework adoption DT support
Hi Markus, On 07/11/2014 06:15 PM, Markus Mayer wrote: On 11 July 2014 15:04, Suman Anna s-a...@ti.com wrote: Hi, This is a refresh of the OMAP Mailbox framework adoption DT support series [1], to work with the revised OMAP mailbox DT/hwmod cleanup series [2]. The series has one less patch than the previous series, with the patch mailbox/omap: add a custom of_xlate function squashed into the OMAP mailbox framework adaptation patch. The first 3 patches deal with the OMAP DT bindings and parse support like previous series, and the last 2 patches deal with the mailbox framework adaptation. The testing is also done with the updated v8 version of mailbox framework [3] from Jassi Brar, no changes are required for the v7 to v8 update. The AM335 PM suspend series [4] which relies on this series also does not require any changes. May I ask what branch this series is based upon? I tried a number of branches (3.16-rcX, 3.15, linux-next), and the series won't apply to any of them (other than patch 1/5, which does apply fine, but that also contains no code). There are couple of dependent preparatory series. You probably missed the following in the cover letter. The series depends on the OMAP mailbox cleanup series [5] and the refreshed OMAP mailbox DT/hwmod cleanup series [2]. As long as you pick the two dependent series, they apply fine on any of the 3.16-rcs. I have posted all the series based on 3.16-rc2. Here's a merged branch for your reference (not for pulling though, it has one additional commit to allow me to test on OMAP2) https://github.com/sumananna/mailbox/commits/submit/3.16-rc2-omap-mbox-v8-fwk-v2 The last 2 patches in the series also depend on the mailbox framework patches from Jassi to not throw any build errors if enabled. regards Suman -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv2 0/5] OMAP Mailbox framework adoption DT support
Hi Suman, There are couple of dependent preparatory series. You probably missed the following in the cover letter. The series depends on the OMAP mailbox cleanup series [5] and the refreshed OMAP mailbox DT/hwmod cleanup series [2]. As long as you pick the two dependent series, they apply fine on any of the 3.16-rcs. I have posted all the series based on 3.16-rc2. Here's a merged branch for your reference (not for pulling though, it has one additional commit to allow me to test on OMAP2) https://github.com/sumananna/mailbox/commits/submit/3.16-rc2-omap-mbox-v8-fwk-v2 The last 2 patches in the series also depend on the mailbox framework patches from Jassi to not throw any build errors if enabled. That worked. Thanks for the pointer. FYI, there is a minor merge conflict rebasing the series onto 3.16-rc5. Applying: ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot Using index info to reconstruct a base tree... M arch/arm/mach-omap2/devices.c Falling back to patching base and 3-way merge... Auto-merging arch/arm/mach-omap2/devices.c CONFLICT (content): Merge conflict in arch/arm/mach-omap2/devices.c Failed to merge in the changes. Patch failed at 0029 ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot That's due to this commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1d29a0722f6c38f79785c9ffb911730598de84e2 Regards, -Markus -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv2 0/5] OMAP Mailbox framework adoption DT support
Hi Markus, There are couple of dependent preparatory series. You probably missed the following in the cover letter. The series depends on the OMAP mailbox cleanup series [5] and the refreshed OMAP mailbox DT/hwmod cleanup series [2]. As long as you pick the two dependent series, they apply fine on any of the 3.16-rcs. I have posted all the series based on 3.16-rc2. Here's a merged branch for your reference (not for pulling though, it has one additional commit to allow me to test on OMAP2) https://github.com/sumananna/mailbox/commits/submit/3.16-rc2-omap-mbox-v8-fwk-v2 The last 2 patches in the series also depend on the mailbox framework patches from Jassi to not throw any build errors if enabled. That worked. Thanks for the pointer. FYI, there is a minor merge conflict rebasing the series onto 3.16-rc5. Applying: ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot Using index info to reconstruct a base tree... M arch/arm/mach-omap2/devices.c Falling back to patching base and 3-way merge... Auto-merging arch/arm/mach-omap2/devices.c CONFLICT (content): Merge conflict in arch/arm/mach-omap2/devices.c Failed to merge in the changes. Patch failed at 0029 ARM: OMAP2+: Avoid mailbox legacy device creation for DT-boot That's due to this commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1d29a0722f6c38f79785c9ffb911730598de84e2 OK, thanks, that's because of the removal of the line immediately above the omap_init_mbox() deletion. Anyway, that should be a trivial rebase and the patch contents should remain the same. Once OMAP3 becomes DT-boot only, I will submit a patch to delete the omap_init_mbox(). regards Suman -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCHv2 0/5] OMAP Mailbox framework adoption DT support
Hi, This is a refresh of the OMAP Mailbox framework adoption DT support series [1], to work with the revised OMAP mailbox DT/hwmod cleanup series [2]. The series has one less patch than the previous series, with the patch mailbox/omap: add a custom of_xlate function squashed into the OMAP mailbox framework adaptation patch. The first 3 patches deal with the OMAP DT bindings and parse support like previous series, and the last 2 patches deal with the mailbox framework adaptation. The testing is also done with the updated v8 version of mailbox framework [3] from Jassi Brar, no changes are required for the v7 to v8 update. The AM335 PM suspend series [4] which relies on this series also does not require any changes. Changes in v2: - Updated the OMAP DT bindings document for the added back DT properties: ti,mbox-num-users and ti,mbox-num-fifos. Also added information regarding #mbox-cells and DT client usage. - Updated the OMAP DT adaptation patch to parse the added back DT properties and clean up the previous match data structure. - Squashed custom xlate patch into the framework adaptation patch. - Tested against v8 of mailbox framework. v1: - Tested against v7 of mailbox framework - See [1] for additional details The series depends on the OMAP mailbox cleanup series [5] and the refreshed OMAP mailbox DT/hwmod cleanup series [2]. The following shows the boot/validation logs on various OMAP platforms: OMAP3 (BeagleXM) : http://slexy.org/view/s23mLEA46B OMAP4 (PandaBoard): http://slexy.org/view/s215xfwEo3 OMAP5 (OMAP5 uEVM): http://slexy.org/view/s2peigexO0 DRA7 (DRA7 EVM) : http://slexy.org/view/s21huoN7Q4 AM33xx (BeagleBone Black) : http://slexy.org/view/s21KQ0gMN8 AM43xx (AM437x GP EVM): http://slexy.org/view/s2KGKGeFre [1] http://www.spinics.net/lists/linux-omap/msg108595.html [2] http://marc.info/?l=linux-omapm=140511512208519w=2 [3] https://lkml.org/lkml/2014/7/11/174 [4] http://www.spinics.net/lists/linux-omap/msg109331.html [5] http://www.spinics.net/lists/linux-omap/msg108574.html Suman Anna (5): 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 .../devicetree/bindings/mailbox/omap-mailbox.txt | 135 ++ 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 | 499 ++--- 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, 584 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-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv2 0/5] OMAP Mailbox framework adoption DT support
On 11 July 2014 15:04, Suman Anna s-a...@ti.com wrote: Hi, This is a refresh of the OMAP Mailbox framework adoption DT support series [1], to work with the revised OMAP mailbox DT/hwmod cleanup series [2]. The series has one less patch than the previous series, with the patch mailbox/omap: add a custom of_xlate function squashed into the OMAP mailbox framework adaptation patch. The first 3 patches deal with the OMAP DT bindings and parse support like previous series, and the last 2 patches deal with the mailbox framework adaptation. The testing is also done with the updated v8 version of mailbox framework [3] from Jassi Brar, no changes are required for the v7 to v8 update. The AM335 PM suspend series [4] which relies on this series also does not require any changes. May I ask what branch this series is based upon? I tried a number of branches (3.16-rcX, 3.15, linux-next), and the series won't apply to any of them (other than patch 1/5, which does apply fine, but that also contains no code). Thanks, -Markus -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
