From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Rob Herring <robh@kernel.org>
Cc: Jon Medhurst <tixy@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Punit Agrawal <punit.agrawal@arm.com>,
Arnd Bergmann <arnd@arndb.de>, Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
Kumar Gala <galak@codeaurora.org>,
Will Deacon <will.deacon@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
DRI devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/4] drm: arm: Add DT bindings documentation for HDLCD driver.
Date: Fri, 13 Nov 2015 10:11:56 +0000 [thread overview]
Message-ID: <20151113101156.GE963@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAL_Jsq+M8cEgLpRJ9j_ULRaGcLgaTZ8rr2F1nv7wUxfEEpZinw@mail.gmail.com>
On Thu, Nov 12, 2015 at 09:30:31PM -0600, Rob Herring wrote:
> On Thu, Nov 12, 2015 at 4:42 AM, Liviu Dudau <Liviu.Dudau@arm.com> wrote:
> > On Wed, Nov 11, 2015 at 12:48:50PM -0600, Rob Herring wrote:
> >> On Wed, Nov 11, 2015 at 04:06:47PM +0000, Liviu Dudau wrote:
> >> > Cc: Rob Herring <robh+dt@kernel.org>
> >> > Cc: Pawel Moll <pawel.moll@arm.com>
> >> > Cc: Mark Rutland <mark.rutland@arm.com>
> >> > Cc: Ian Campbell <ijc+devicetree@hellion.org.uk>
> >> > Cc: Kumar Gala <galak@codeaurora.org>
> >> >
> >> > Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
> >>
> >> Looks pretty good, but a few comments.
> >>
> >> > ---
> >> > .../devicetree/bindings/drm/arm/arm,hdlcd.txt | 74 ++++++++++++++++++++++
> >> > 1 file changed, 74 insertions(+)
> >> > create mode 100644 Documentation/devicetree/bindings/drm/arm/arm,hdlcd.txt
> >> >
> >> > diff --git a/Documentation/devicetree/bindings/drm/arm/arm,hdlcd.txt b/Documentation/devicetree/bindings/drm/arm/arm,hdlcd.txt
> >> > new file mode 100644
> >> > index 0000000..b57f1b9
> >> > --- /dev/null
> >> > +++ b/Documentation/devicetree/bindings/drm/arm/arm,hdlcd.txt
> >> > @@ -0,0 +1,74 @@
> >> > +ARM HDLCD
> >> > +
> >> > +This is a display controller found on several development platforms produced
> >> > +by ARM Ltd and in more modern of its' Fast Models. The HDLCD is an RGB
> >> > +streamer that reads the data from a framebuffer and sends it to a single
> >> > +digital encoder (DVI or HDMI).
> >> > +
> >> > +Required properties:
> >> > + - compatible: "arm,hdlcd"
> >>
> >> Kind of generic. Something more specific please.
> >
> > "There can be only one!" (hdlcd) :) This is going to be a "one version only" HW part.
> > ARM has now switched to a new display hardware that has more features and a new name,
> > and work on mainlining support for that will start once I get the HDLCD driver accepted.
>
> So there is never going to be a single difference across platforms.
Correct, there is only one implementation available. AFAIK there are no plans to make changes to it.
> Variations in max clock for different FPGAs?
The clock is external to the part and there is a check in the driver if we can set the frequency
to match the requested dotclock by the video_mode. It does not affect the hardware or how it presents
itself to the driver.
>
>
> >> > + - reg: Physical base address and length of the controller's registers.
> >> > + If a second pair of address and length values is present this specifies
> >> > + the presence of a DMA coherent memory area that the HDLCD can use as
> >> > + framebuffer instead of normal CMA memory.
> >>
> >> This is on-chip RAM or nornal system RAM? We already have bindings for
> >> both.
> >
> > Juno has a set of TLX (ThinLinks) connectors on the board where an FPGA can be attached. On r1
> > the code running on FPGA can even participate as an AXI master with full coherency. The FPGA
> > has local memory that we want to share with the HDLCD to be used as a framebuffer.
>
> So describe the memory region and then use a memory-region phandle to
> the memory here.
OK, I will.
>
> >> > + - interrupts: One interrupt used by the display controller to notify the
> >> > + interrupt controller when any of the interrupt sources programmed in
> >> > + the interrupt mask register have activated.
> >> > + - clocks: A list of phandle + clock-specifier pairs, one for each
> >> > + entry in 'clock-names'.
> >> > + - clock-names: A list of clock names. For HDLD it should contain:
>
> typo: HDLD
oops, thanks, will fix.
>
> >> > + - "pxlclk" for the clock feeding the output PLL of the controller.
> >> > + - port: The HDLCD connection to an encoder chip. The connection is modelled
>
> s/modelled/modeled/
ditto.
Thanks for reviewing it,
Liviu
>
> Rob
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-13 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:06 [PATCH v2 0/4] drm: Add support for the ARM HDLCD display controller Liviu Dudau
2015-11-11 16:06 ` [PATCH v2 1/4] drm: arm: Add DT bindings documentation for HDLCD driver Liviu Dudau
2015-11-11 18:48 ` Rob Herring
2015-11-12 10:42 ` Liviu Dudau
2015-11-12 10:52 ` Jon Medhurst (Tixy)
[not found] ` <1447325545.2825.9.camel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-11-12 11:09 ` Liviu Dudau
2015-11-13 3:30 ` Rob Herring
2015-11-13 10:11 ` Liviu Dudau [this message]
2015-11-11 16:06 ` [PATCH v2 2/4] drm: Add support for ARM's HDLCD controller Liviu Dudau
2015-11-11 16:06 ` [PATCH v2 3/4] arm64: Juno: Add HDLCD support to the Juno boards Liviu Dudau
2015-11-11 16:06 ` [PATCH v2 4/4] MAINTAINERS: Add Liviu Dudau as maintainer for ARM HDLCD driver Liviu Dudau
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=20151113101156.GE963@e106497-lin.cambridge.arm.com \
--to=liviu.dudau@arm.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=punit.agrawal@arm.com \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tixy@linaro.org \
--cc=will.deacon@arm.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