From: Rajendra Nayak <rnayak@ti.com> To: bcousson@baylibre.com, paul@pwsan.com, tony@atomide.com Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, Rajendra Nayak <rnayak@ti.com> Subject: [PATCH v2 0/5] OMAP: Add DT bindings to specify when devices should not be idled or reset Date: Wed, 9 Oct 2013 15:41:56 +0530 [thread overview] Message-ID: <1381313521-10422-1-git-send-email-rnayak@ti.com> (raw) Changes in v2: * Patches are split in such a way that DT and hwmod changes are kept in seperate patches so they can be pulled in by Benoit and Paul seperately. * Binding names are slightly updated to address the concern from Tony and Benoit [1] * Added a patch [5/5] to prevent GPIO reset on AM335x EVM-SK board, which was also the original motivation of this series since the board fails to boot from mainline despite support for AM335x and a am335x-evmsk.dts file existing in mainline for quite a while. We have devices like co-processors, SoC internal busses, memory controllers etc which should not be idled or reset. In some cases erratas around IP blocks prevent them from either being idled or reset. Have a way to pass this information from Device tree, and get rid of similar information that exists as part of the omap_hwmod data files for various DT only OMAP SoCs. Boot tested on OMAP4 panda es, AM335x EVM and AM335x EVM-SK [1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg94349.html Rajendra Nayak (5): ARM: OMAP2+: hwmod: cleanup HWMOD_INIT_NO_RESET usage ARM: dts: omap: Add new bindings for OMAP ARM: OMAP2+: hwmod: Extract no-idle and no-reset info from DT ARM: OMAP2+: hwmod: Cleanup usage of HWMOD_INIT_NO_RESET and HWMOD_INIT_NO_IDLE ARM: dts: AM335x-evmsk: Do not reset gpio0 .../devicetree/bindings/arm/omap/omap.txt | 3 ++- arch/arm/boot/dts/am335x-evmsk.dts | 4 ++++ arch/arm/boot/dts/am33xx.dtsi | 2 ++ arch/arm/boot/dts/omap4.dtsi | 3 +++ arch/arm/boot/dts/omap5.dtsi | 2 ++ arch/arm/mach-omap2/omap_hwmod.c | 23 ++++++++++++++------ arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 22 +++++++++---------- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 ++--- arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 4 +--- 9 files changed, 43 insertions(+), 26 deletions(-) -- 1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/5] OMAP: Add DT bindings to specify when devices should not be idled or reset Date: Wed, 9 Oct 2013 15:41:56 +0530 [thread overview] Message-ID: <1381313521-10422-1-git-send-email-rnayak@ti.com> (raw) Changes in v2: * Patches are split in such a way that DT and hwmod changes are kept in seperate patches so they can be pulled in by Benoit and Paul seperately. * Binding names are slightly updated to address the concern from Tony and Benoit [1] * Added a patch [5/5] to prevent GPIO reset on AM335x EVM-SK board, which was also the original motivation of this series since the board fails to boot from mainline despite support for AM335x and a am335x-evmsk.dts file existing in mainline for quite a while. We have devices like co-processors, SoC internal busses, memory controllers etc which should not be idled or reset. In some cases erratas around IP blocks prevent them from either being idled or reset. Have a way to pass this information from Device tree, and get rid of similar information that exists as part of the omap_hwmod data files for various DT only OMAP SoCs. Boot tested on OMAP4 panda es, AM335x EVM and AM335x EVM-SK [1] http://www.mail-archive.com/linux-omap at vger.kernel.org/msg94349.html Rajendra Nayak (5): ARM: OMAP2+: hwmod: cleanup HWMOD_INIT_NO_RESET usage ARM: dts: omap: Add new bindings for OMAP ARM: OMAP2+: hwmod: Extract no-idle and no-reset info from DT ARM: OMAP2+: hwmod: Cleanup usage of HWMOD_INIT_NO_RESET and HWMOD_INIT_NO_IDLE ARM: dts: AM335x-evmsk: Do not reset gpio0 .../devicetree/bindings/arm/omap/omap.txt | 3 ++- arch/arm/boot/dts/am335x-evmsk.dts | 4 ++++ arch/arm/boot/dts/am33xx.dtsi | 2 ++ arch/arm/boot/dts/omap4.dtsi | 3 +++ arch/arm/boot/dts/omap5.dtsi | 2 ++ arch/arm/mach-omap2/omap_hwmod.c | 23 ++++++++++++++------ arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 22 +++++++++---------- arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 ++--- arch/arm/mach-omap2/omap_hwmod_54xx_data.c | 4 +--- 9 files changed, 43 insertions(+), 26 deletions(-) -- 1.7.9.5
next reply other threads:[~2013-10-09 10:11 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-09 10:11 Rajendra Nayak [this message] 2013-10-09 10:11 ` [PATCH v2 0/5] OMAP: Add DT bindings to specify when devices should not be idled or reset Rajendra Nayak 2013-10-09 10:11 ` [PATCH v2 1/5] ARM: OMAP2+: hwmod: cleanup HWMOD_INIT_NO_RESET usage Rajendra Nayak 2013-10-09 10:11 ` Rajendra Nayak 2013-10-09 14:55 ` Paul Walmsley 2013-10-09 14:55 ` Paul Walmsley 2013-10-09 10:11 ` [PATCH v2 2/5] ARM: dts: omap: Add new bindings for OMAP Rajendra Nayak 2013-10-09 10:11 ` Rajendra Nayak 2013-10-09 15:13 ` Benoit Cousson 2013-10-09 15:13 ` Benoit Cousson 2013-10-09 16:41 ` Rajendra Nayak 2013-10-09 16:41 ` Rajendra Nayak 2013-10-09 16:45 ` Benoit Cousson 2013-10-09 16:45 ` Benoit Cousson 2013-10-15 7:27 ` Benoit Cousson 2013-10-15 7:27 ` Benoit Cousson 2013-10-15 8:23 ` Rajendra Nayak 2013-10-15 8:23 ` Rajendra Nayak 2013-10-09 10:11 ` [PATCH v2 3/5] ARM: OMAP2+: hwmod: Extract no-idle and no-reset info from DT Rajendra Nayak 2013-10-09 10:11 ` Rajendra Nayak 2013-10-09 14:55 ` Paul Walmsley 2013-10-09 14:55 ` Paul Walmsley 2013-10-09 10:12 ` [PATCH v2 4/5] ARM: OMAP2+: hwmod: Cleanup usage of HWMOD_INIT_NO_RESET and HWMOD_INIT_NO_IDLE Rajendra Nayak 2013-10-09 10:12 ` Rajendra Nayak 2013-10-09 10:12 ` [PATCH v2 5/5] ARM: dts: AM335x-evmsk: Do not reset gpio0 Rajendra Nayak 2013-10-09 10:12 ` Rajendra Nayak 2013-10-10 16:44 ` [PATCH] ARM: dts: omap4-panda-es: Do not reset gpio1 Nishanth Menon 2013-10-10 16:44 ` Nishanth Menon 2013-10-10 16:44 ` Nishanth Menon 2013-10-10 16:47 ` Tony Lindgren 2013-10-10 16:47 ` Tony Lindgren 2013-10-10 19:01 ` Nishanth Menon 2013-10-10 19:01 ` Nishanth Menon 2013-10-10 19:01 ` Nishanth Menon 2013-10-15 7:28 ` Benoit Cousson 2013-10-15 7:28 ` Benoit Cousson
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=1381313521-10422-1-git-send-email-rnayak@ti.com \ --to=rnayak@ti.com \ --cc=bcousson@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=paul@pwsan.com \ --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: linkBe 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.