From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: linux-fbdev@vger.kernel.org,
Florian Tobias Schandinat <FlorianSchandinat@gmx.de>,
devicetree-discuss@lists.ozlabs.org,
Rob Herring <rob.herring@calxeda.com>,
Sascha Hauer <kernel@pengutronix.de>,
Markus Pargmann <mpa@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/2] video: imxfb: Add DT support
Date: Mon, 15 Apr 2013 15:23:22 +0200 [thread overview]
Message-ID: <20130415132322.GC15139@game.jcrosoft.org> (raw)
In-Reply-To: <20130415151316.4d49e9b2@e6520eb>
On 15:13 Mon 15 Apr , Eric Bénard wrote:
> Hi,
>
> Le Mon, 15 Apr 2013 14:43:21 +0200,
> Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> a écrit :
>
> > On 16:31 Sun 14 Apr , Markus Pargmann wrote:
> > > On Mon, Apr 08, 2013 at 09:57:42AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > On 12:31 Fri 05 Apr , Markus Pargmann wrote:
> > > > > Add devicetree support for imx framebuffer driver. It uses the generic
> > > > > display bindings and helper functions.
> > > > >
> > > > > Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> > > > > Cc: Fabio Estevam <festevam@gmail.com>
> > > > > Cc: Mark Rutland <mark.rutland@arm.com>
> > > > > ---
> > > > > .../devicetree/bindings/video/fsl,imx-fb.txt | 49 ++++++
> > > > > drivers/video/imxfb.c | 192 +++++++++++++++++----
> > > > > 2 files changed, 207 insertions(+), 34 deletions(-)
> > > > > create mode 100644 Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > > > >
> > > > > diff --git a/Documentation/devicetree/bindings/video/fsl,imx-fb.txt b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > > > > new file mode 100644
> > > > > index 0000000..bde9c77
> > > > > --- /dev/null
> > > > > +++ b/Documentation/devicetree/bindings/video/fsl,imx-fb.txt
> > > > > @@ -0,0 +1,49 @@
> > > > > +Freescale imx21 Framebuffer
> > > > > +
> > > > > +This framebuffer driver supports devices imx1, imx21, imx25, and imx27.
> > > > > +
> > > > > +Required properties:
> > > > > +- compatible : "fsl,<chip>-fb", chip should be imx1 or imx21
> > > > > +- reg : Should contain 1 register ranges(address and length)
> > > > > +- interrupts : One interrupt of the fb dev
> > > > > +
> > > > > +Required nodes:
> > > > > +- display: Phandle to a display node as described in
> > > > > + Documentation/devicetree/bindings/video/display-timing.txt
> > > > > + Additional, the display node has to define properties:
> > > > > + - fsl,bpp: Bits per pixel
> > > > > + - fsl,pcr: LCDC PCR value
> > > > > +
> > > > > +Optional properties:
> > > > > +- dmacr-eukrea: Should be set for eukrea boards.
> > > > why ?
> > >
> > > Because eukrea boards have a different dmacr then all other boards using
> > > imxfb. The dmacr address is hardcoded as defaults in the code. I could
> > > also search for the board name in the DT, but there are no eukrea boards
> > > with DT at the moment, so I thought a bool property may be better for
> > > the moment.
> > so no if an other board come will have an other property no
> >
> > add an optionnal option to pass the dmacr
>
> I didn't follow the thread but dmacr is not specific to our boards :
> $ grep -rn dmacr arch/arm/mach-imx/
> arch/arm/mach-imx/mach-mx27_3ds.c:446: .dmacr = 0x00020010,
> arch/arm/mach-imx/mach-mx21ads.c:231: .dmacr = 0x00020008,
> arch/arm/mach-imx/mach-mxt_td60.c:210: .dmacr = 0x00020010,
> arch/arm/mach-imx/eukrea_mbimx27-baseboard.c:192: .dmacr = 0x00040060,
> arch/arm/mach-imx/eukrea_mbimxsd25-baseboard.c:165: .dmacr = 0x00040060,
> arch/arm/mach-imx/mach-mx27ads.c:241: .dmacr = 0x00020010,
> arch/arm/mach-imx/mach-pca100.c:351: .dmacr = 0x00020010,
> arch/arm/mach-imx/pcm970-baseboard.c:185: .dmacr = 0x00020010,
> arch/arm/mach-imx/mach-mx25_3ds.c:173: .dmacr = 0x00020010,
with this it even more clear nack on the dmacr-eukrea property
use an optional property where we can specify the value to use
Best Regsrds,
J.
next prev parent reply other threads:[~2013-04-15 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 10:31 [PATCH v3 0/2] video: imxfb DT support Markus Pargmann
2013-04-05 10:31 ` [PATCH v3 1/2] imxfb: Set alpha value of the framebuffer Markus Pargmann
2013-04-05 10:31 ` [PATCH v3 2/2] video: imxfb: Add DT support Markus Pargmann
[not found] ` <1365157876-1757-3-git-send-email-mpa-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2013-04-08 7:57 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20130408075742.GR20693-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2013-04-14 14:31 ` Markus Pargmann
2013-04-15 12:43 ` Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20130415124321.GB15139-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2013-04-15 13:13 ` Eric Bénard
2013-04-15 13:23 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
[not found] ` <20130415132322.GC15139-RQcB7r2h9QmfDR2tN2SG5Ni2O/JbrIOy@public.gmane.org>
2013-04-16 14:17 ` Markus Pargmann
2013-04-15 19:47 ` Sascha Hauer
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=20130415132322.GC15139@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=FlorianSchandinat@gmx.de \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eric@eukrea.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=rob.herring@calxeda.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).