From: Tomi Valkeinen <tomi.valkeinen@ti.com> To: archit@ti.com, tony@atomide.com, linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: b-cousson@ti.com, s-guiriec@ti.com, Tomi Valkeinen <tomi.valkeinen@ti.com> Subject: [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Date: Mon, 5 Nov 2012 15:14:13 +0200 [thread overview] Message-ID: <1352121259-5836-1-git-send-email-tomi.valkeinen@ti.com> (raw) Hi, OMAPDSS device tree support is still some way in the future. Tony has requested to get DSS working for Panda & SDP boards with DT kernel, so that we'll have fully working boards with DT. This series makes a few hacks to get a working display on OMAP4 Panda and SDP boards. The idea is to setup the omapdss with the non-DT method, creating the omapdss devices and passing platform data to them. This setup code is called from board-generic for Panda and SDP boards. There was one problem with this approach: omapdss cannot get regulators using the omapdss's names fro the regulators. Thus there's a hack patch to get the regulators using the OMAP4 "native" regulator names, thus circumventing the problem. Tony, if these look good, how do you want to merge these? There are three parts here, and I think they can be merged independently if so wished: * .dts changes for the pinmuxing (2 patches) * dss-common.c and board-generic.c changes (3 patches) * DSS hack for the regulators (1 patch) If one of those parts is missing, DSS won't start with DT kernel, but otherwise there shouldn't be any problems. So to avoid conflicts, I suggest that you take the first two parts, and I'll merge the DSS hack via omapdss tree. Tomi Ricardo Neri (2): ARM/dts: omap4-panda: Add pinmux configuration for HDMI ARM/dts: omap4-sdp: Add pinmux configuration for HDMI Tomi Valkeinen (4): OMAPDSS: HACK: look for regulators with omap4 names OMAP: panda: move display init from board file to dss-common.c OMAP: omap4sdp: move display init from board file to dss-common.c OMAP: board-generic: enable DSS for panda & sdp boards arch/arm/boot/dts/omap4-panda-a4.dts | 17 ++ arch/arm/boot/dts/omap4-panda.dts | 18 ++ arch/arm/boot/dts/omap4-pandaES.dts | 9 + arch/arm/boot/dts/omap4-sdp-es23plus.dts | 17 ++ arch/arm/boot/dts/omap4-sdp.dts | 18 ++ arch/arm/mach-omap2/Makefile | 2 +- arch/arm/mach-omap2/board-4430sdp.c | 157 +---------------- arch/arm/mach-omap2/board-generic.c | 10 ++ arch/arm/mach-omap2/board-omap4panda.c | 68 +------- arch/arm/mach-omap2/dss-common.c | 276 ++++++++++++++++++++++++++++++ arch/arm/mach-omap2/dss-common.h | 14 ++ drivers/video/omap2/dss/dsi.c | 8 + drivers/video/omap2/dss/hdmi.c | 4 + 13 files changed, 394 insertions(+), 224 deletions(-) create mode 100644 arch/arm/boot/dts/omap4-panda-a4.dts create mode 100644 arch/arm/boot/dts/omap4-sdp-es23plus.dts create mode 100644 arch/arm/mach-omap2/dss-common.c create mode 100644 arch/arm/mach-omap2/dss-common.h -- 1.7.10.4
WARNING: multiple messages have this Message-ID (diff)
From: tomi.valkeinen@ti.com (Tomi Valkeinen) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Date: Mon, 5 Nov 2012 15:14:13 +0200 [thread overview] Message-ID: <1352121259-5836-1-git-send-email-tomi.valkeinen@ti.com> (raw) Hi, OMAPDSS device tree support is still some way in the future. Tony has requested to get DSS working for Panda & SDP boards with DT kernel, so that we'll have fully working boards with DT. This series makes a few hacks to get a working display on OMAP4 Panda and SDP boards. The idea is to setup the omapdss with the non-DT method, creating the omapdss devices and passing platform data to them. This setup code is called from board-generic for Panda and SDP boards. There was one problem with this approach: omapdss cannot get regulators using the omapdss's names fro the regulators. Thus there's a hack patch to get the regulators using the OMAP4 "native" regulator names, thus circumventing the problem. Tony, if these look good, how do you want to merge these? There are three parts here, and I think they can be merged independently if so wished: * .dts changes for the pinmuxing (2 patches) * dss-common.c and board-generic.c changes (3 patches) * DSS hack for the regulators (1 patch) If one of those parts is missing, DSS won't start with DT kernel, but otherwise there shouldn't be any problems. So to avoid conflicts, I suggest that you take the first two parts, and I'll merge the DSS hack via omapdss tree. Tomi Ricardo Neri (2): ARM/dts: omap4-panda: Add pinmux configuration for HDMI ARM/dts: omap4-sdp: Add pinmux configuration for HDMI Tomi Valkeinen (4): OMAPDSS: HACK: look for regulators with omap4 names OMAP: panda: move display init from board file to dss-common.c OMAP: omap4sdp: move display init from board file to dss-common.c OMAP: board-generic: enable DSS for panda & sdp boards arch/arm/boot/dts/omap4-panda-a4.dts | 17 ++ arch/arm/boot/dts/omap4-panda.dts | 18 ++ arch/arm/boot/dts/omap4-pandaES.dts | 9 + arch/arm/boot/dts/omap4-sdp-es23plus.dts | 17 ++ arch/arm/boot/dts/omap4-sdp.dts | 18 ++ arch/arm/mach-omap2/Makefile | 2 +- arch/arm/mach-omap2/board-4430sdp.c | 157 +---------------- arch/arm/mach-omap2/board-generic.c | 10 ++ arch/arm/mach-omap2/board-omap4panda.c | 68 +------- arch/arm/mach-omap2/dss-common.c | 276 ++++++++++++++++++++++++++++++ arch/arm/mach-omap2/dss-common.h | 14 ++ drivers/video/omap2/dss/dsi.c | 8 + drivers/video/omap2/dss/hdmi.c | 4 + 13 files changed, 394 insertions(+), 224 deletions(-) create mode 100644 arch/arm/boot/dts/omap4-panda-a4.dts create mode 100644 arch/arm/boot/dts/omap4-sdp-es23plus.dts create mode 100644 arch/arm/mach-omap2/dss-common.c create mode 100644 arch/arm/mach-omap2/dss-common.h -- 1.7.10.4
next reply other threads:[~2012-11-05 13:14 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-05 13:14 Tomi Valkeinen [this message] 2012-11-05 13:14 ` [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Tomi Valkeinen 2012-11-05 13:14 ` [PATCH 1/6] ARM/dts: omap4-panda: Add pinmux configuration for HDMI Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-05 13:17 ` Tomi Valkeinen 2012-11-05 13:17 ` Tomi Valkeinen 2012-11-06 5:24 ` Ricardo Neri 2012-11-06 5:24 ` Ricardo Neri 2012-11-05 17:43 ` Benoit Cousson 2012-11-05 17:43 ` Benoit Cousson 2012-11-07 10:56 ` Benoit Cousson 2012-11-07 10:56 ` Benoit Cousson 2012-11-13 19:10 ` Ricardo Neri 2012-11-13 19:10 ` Ricardo Neri 2012-11-14 7:39 ` Tomi Valkeinen 2012-11-14 7:39 ` Tomi Valkeinen 2012-11-05 13:14 ` [PATCH 2/6] ARM/dts: omap4-sdp: " Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-07 10:57 ` Benoit Cousson 2012-11-07 10:57 ` Benoit Cousson 2012-11-05 13:14 ` [PATCH 3/6] OMAPDSS: HACK: look for regulators with omap4 names Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-05 13:14 ` [PATCH 4/6] OMAP: panda: move display init from board file to dss-common.c Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-05 13:14 ` [PATCH 5/6] OMAP: omap4sdp: " Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-05 13:14 ` [PATCH 6/6] OMAP: board-generic: enable DSS for panda & sdp boards Tomi Valkeinen 2012-11-05 13:14 ` Tomi Valkeinen 2012-11-07 1:04 ` [PATCH 0/6] OMAPDSS: enable DSS for Panda & SDP with devtree Tony Lindgren 2012-11-07 1:04 ` Tony Lindgren 2012-11-07 10:58 ` Benoit Cousson 2012-11-07 10:58 ` Benoit Cousson 2012-11-07 21:34 ` Tony Lindgren 2012-11-07 21:34 ` Tony Lindgren
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=1352121259-5836-1-git-send-email-tomi.valkeinen@ti.com \ --to=tomi.valkeinen@ti.com \ --cc=archit@ti.com \ --cc=b-cousson@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=s-guiriec@ti.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.