From: Chanho Park <chanho61.park@samsusng.com>
To: 'Inki Dae' <inki.dae@samsung.com>, 'Mark Rutland' <mark.rutland@arm.com>
Cc: kgene.kim@samsung.com, linux-samsung-soc@vger.kernel.org,
jy0922.shim@samsung.com, sw0312.kim@samsung.com,
dri-devel@lists.freedesktop.org, kyungmin.park@samsung.com,
linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH 2/3] drm/exynos: add dt-binding documentation for rotator
Date: Tue, 23 Jul 2013 11:47:00 +0900 [thread overview]
Message-ID: <00fb01ce874e$e7807f40$b6817dc0$@samsusng.com> (raw)
In-Reply-To: <007f01ce8744$f3d1c560$db755020$%dae@samsung.com>
> -----Original Message-----
> From: Inki Dae [mailto:inki.dae@samsung.com]
> Sent: Tuesday, July 23, 2013 10:36 AM
> To: 'Chanho Park'; 'Mark Rutland'; 'Chanho Park'
> Cc: kgene.kim@samsung.com; linux-samsung-soc@vger.kernel.org;
> jy0922.shim@samsung.com; sw0312.kim@samsung.com; dri-
> devel@lists.freedesktop.org; kyungmin.park@samsung.com; linux-arm-
> kernel@lists.infradead.org
> Subject: RE: [PATCH 2/3] drm/exynos: add dt-binding documentation for
> rotator
>
>
>
> > -----Original Message-----
> > From: Chanho Park [mailto:chanho61.park@samsusng.com]
> > Sent: Tuesday, July 23, 2013 10:22 AM
> > To: 'Mark Rutland'; 'Chanho Park'
> > Cc: inki.dae@samsung.com; kgene.kim@samsung.com; linux-samsung-
> > soc@vger.kernel.org; jy0922.shim@samsung.com; sw0312.kim@samsung.com;
> > dri- devel@lists.freedesktop.org; kyungmin.park@samsung.com;
> > linux-arm- kernel@lists.infradead.org
> > Subject: RE: [PATCH 2/3] drm/exynos: add dt-binding documentation for
> > rotator
> >
> > Hi Mark,
> > Thank you for your review.
> >
> > > -----Original Message-----
> > > From: Mark Rutland [mailto:mark.rutland@arm.com]
> > > Sent: Monday, July 22, 2013 5:48 PM
> > > To: Chanho Park
> > > Cc: inki.dae@samsung.com; kgene.kim@samsung.com; linux-samsung-
> > > soc@vger.kernel.org; jy0922.shim@samsung.com; devicetree-
> > > discuss@lists.ozlabs.org; sw0312.kim@samsung.com; dri-
> > > devel@lists.freedesktop.org; kyungmin.park@samsung.com; linux-arm-
> > > kernel@lists.infradead.org
> > > Subject: Re: [PATCH 2/3] drm/exynos: add dt-binding documentation
> > > for rotator
> > >
> > > On Mon, Jul 22, 2013 at 07:49:26AM +0100, Chanho Park wrote:
> > > > This patch adds a dt-binding document for exynos rotator. It
> > > > describes which nodes should be defined to use the rotator.
> > > >
> > > > Signed-off-by: Chanho Park <chanho61.park@samsung.com>
> > > > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > > > ---
> > > > .../bindings/drm/exynos/samsung-rotator.txt | 35
> > > ++++++++++++++++++++
> > > > 1 file changed, 35 insertions(+)
> > > > create mode 100644
> > > > Documentation/devicetree/bindings/drm/exynos/samsung-rotator.txt
> > > >
> > > > diff --git
> > > > a/Documentation/devicetree/bindings/drm/exynos/samsung-rotator.txt
> > > > b/Documentation/devicetree/bindings/drm/exynos/samsung-rotator.txt
> > > > new file mode 100644
> > > > index 0000000..6b1d704
> > > > --- /dev/null
> > > > +++ b/Documentation/devicetree/bindings/drm/exynos/samsung-rotator
> > > > +++ .txt
> > > > @@ -0,0 +1,35 @@
> > > > +* Samsung Image Rotator
> > > > +
> > > > +Required properties:
> > > > + - compatible : value should be the "samsung,exynos4210".
> > > > + - reg : Physical base address of the IP registers and length of
> > > memory
> > > > + mapped region.
> > > > + - interrupts : interrupt number to the CPU.
> > > > + - clocks : clock number of exynos4 rotator clock.
> > > > + - clocks : clock name of rotator
> > >
> > > clock-names?
> >
> > Yes. It seems to have a mistake during copy and paste.
> > I'll modify it next patch.
> >
> > >
> > > > + - status : "okay" or "disabled"
> > > > + - limit table for image formats : min_w/min_h/max_w/max_h for
> > > > + min/max of image
> > >
> > > Limit table? This doesn't seem to be a well-defined binding, and it
> > > seems like a relatively generic thing to describe.
> > >
> > > > +
> > > > +Example:
> > > > + rotator: rotator@12810000 {
> > > > + compatible = "samsung,exynos4210-rotator";
> > > > + reg = <0x12810000 0x1000>;
> > > > + interrupts = <0 83 0>;
> > > > + clocks = <&clock 278>;
> > > > + clock-names = "rotator";
> > > > + status = "disabled";
> > > > + ycbcr420_2p {
> > >
> > > Which names are allowed for these subnodes?
> > >
> > > > + min_w = <32>;
> > > > + min_h = <32>;
> > > > + max_w = <32768>;
> > > > + max_h = <32768>;
> > > > + align = <3>;
> > >
> > > min-width, min-height, max-width, max-height? What units are they in?
> > >
> > > What does alignment specify exactly?
> > >
> > > Are these a configurable part of the rotator hardware, or are these
> > > values always the same? If thery're always the same, there's no need
> > > to describe in in the devicetree.
> >
> > I've checked the rotator limitation for all of exynos4 chipsets and
> > exynos5250.
> > As a result, these have same value.
>
> Not true. See the Exynos4210 user manual again. At least, the manual
> says maximum size is 64k x 64k in case of Y components.
Yes. The exynos4210 has different maximum limits of RGB888/YCbCr420 2p
compared with any other SoCs(exynos4x12/exynos5250).
I'll make a next patch with considering it.
Thanks
Best Regards,
Chanho Park.
>
> > I think it seems to be better leave on static value.
> > I'll prepare next patches including your suggestion.
> >
>
> So, you should consider such a little bit difference.
>
> > Thanks
> >
> > Best Regards,
> > Chanho Park
> >
> > >
> > > Thanks,
> > > Mark.
> > >
> > > > + };
> > > > + rgb888 {
> > > > + min_w = <8>;
> > > > + min_h = <8>;
> > > > + max_w = <8192>;
> > > > + max_h = <8192>;
> > > > + align = <2>;
> > > > + };
> > > > + };
> > > > --
> > > > 1.7.9.5
> > > >
> > > >
> > > > _______________________________________________
> > > > linux-arm-kernel mailing list
> > > > linux-arm-kernel@lists.infradead.org
> > > > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> > > >
next prev parent reply other threads:[~2013-07-23 2:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 6:49 [PATCH 0/3] device tree support for exynos rotator Chanho Park
2013-07-22 6:49 ` Chanho Park
2013-07-22 6:49 ` [PATCH 1/3] drm/exynos: add device tree support for rotator Chanho Park
2013-07-22 6:49 ` Chanho Park
2013-07-22 12:20 ` Inki Dae
2013-07-22 12:20 ` Inki Dae
2013-07-22 19:32 ` Tomasz Figa
2013-07-22 19:32 ` Tomasz Figa
2013-07-22 6:49 ` [PATCH 2/3] drm/exynos: add dt-binding documentation " Chanho Park
2013-07-22 6:49 ` Chanho Park
2013-07-22 8:48 ` Mark Rutland
2013-07-22 8:48 ` Mark Rutland
2013-07-22 12:37 ` Inki Dae
2013-07-22 12:37 ` Inki Dae
2013-07-22 12:46 ` Lucas Stach
2013-07-22 12:46 ` Lucas Stach
2013-07-22 13:31 ` Inki Dae
2013-07-22 13:31 ` Inki Dae
2013-07-22 14:00 ` Sylwester Nawrocki
2013-07-22 14:00 ` Sylwester Nawrocki
2013-07-22 19:28 ` Tomasz Figa
2013-07-22 19:28 ` Tomasz Figa
2013-07-23 2:00 ` Inki Dae
2013-07-23 2:00 ` Inki Dae
2013-07-23 1:21 ` Chanho Park
2013-07-23 1:35 ` Inki Dae
2013-07-23 1:35 ` Inki Dae
2013-07-23 2:47 ` Chanho Park [this message]
2013-07-22 6:49 ` [PATCH 3/3] dts: ARM: add a rotator node for exynos4 Chanho Park
2013-07-22 6:49 ` Chanho Park
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='00fb01ce874e$e7807f40$b6817dc0$@samsusng.com' \
--to=chanho61.park@samsusng.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=sw0312.kim@samsung.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 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.