linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jacopo Mondi <jacopo@jmondi.org>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	VenkataRajesh.Kalakodima@in.bosch.com,
	Harsha.ManjulaMallikarjun@in.bosch.com
Subject: Re: [RFC 1/9] dt-bindings: display: renesas,cmm: Add R-Car CMM documentation
Date: Tue, 28 May 2019 16:50:18 +0200	[thread overview]
Message-ID: <CAMuHMdV3ar8JnPo0S-MEUgPdNSDp8jKG95Tq_483ydn0swZqqA@mail.gmail.com> (raw)
In-Reply-To: <20190528142520.GA14336@pendragon.ideasonboard.com>

Hi Laurent,

On Tue, May 28, 2019 at 4:31 PM Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Tue, May 28, 2019 at 02:37:25PM +0200, Jacopo Mondi wrote:
> > On Sat, May 11, 2019 at 09:16:18PM +0300, Laurent Pinchart wrote:
> > > On Wed, May 08, 2019 at 07:34:20PM +0200, Jacopo Mondi wrote:
> > >> Add device tree bindings documentation for the Renesas R-Car Display
> > >> Unit Color Management Module.
> > >>
> > >> CMM is the image enhancement module available on each R-Car DU video
> > >> channel.
> > >
> > > Not on all of them, V3M and V3H don't include a CMM module.
> > >
> > >> Signed-off-by: Jacopo Mondi <jacopo+renesas@jmondi.org>

> > >> --- /dev/null
> > >> +++ b/Documentation/devicetree/bindings/display/renesas,cmm.txt
> > >> @@ -0,0 +1,24 @@
> > >> +* Renesas R-Car Color Management Unit (CMM)
> > >
> > > It's called Color Management Module in the documentation (hence the CMM
> > > abbreviation)
> > >
> > >> +
> > >> +Renesas R-Car image enhancement module connected to R-Car DU video channels.
> > >> +
> > >> +Required properties:
> > >> + - compatible: shall be:
> > >> +   - "renesas,cmm"
> > >
> > > There's a CMM in R-Car Gen2 with a different feature set, so I think you
> > > need at least two compatible strings. As far as I can tell SoC-specific
> > > compatible strings are required.
> >
> > I assume you meant "SoC-specific compatible strings are NOT required" ?
>
> Correct, sorry.
>
> > Could you otherwise specify why do you think we need a per-SoC
> > compatible, since there are no platform specific data (for now, at
> > least, but considering the CMM seems identical in all SoCs I hardly
> > think we will have any in the near future).
> >
> > Ack on the gen2/gen3 specific strings though.

Usually we do define SoC-specific compatible values in the DT bindings,
unless there is a version register, like on the VPSs.

Why would we want to deviate from that practice for the CMM?

Thanks!

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2019-05-28 14:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 17:34 [RFC 0/9] drm: rcar-du: Add CMM support to M3-W (plumbing only) Jacopo Mondi
2019-05-08 17:34 ` [RFC 1/9] dt-bindings: display: renesas,cmm: Add R-Car CMM documentation Jacopo Mondi
2019-05-11 18:16   ` Laurent Pinchart
2019-05-28 12:37     ` Jacopo Mondi
2019-05-28 14:25       ` Laurent Pinchart
2019-05-28 14:50         ` Geert Uytterhoeven [this message]
2019-05-08 17:34 ` [RFC 2/9] dt-bindings: display, renesas,du: Document cmms property Jacopo Mondi
2019-05-11 18:23   ` Laurent Pinchart
2019-05-15 14:12     ` Jacopo Mondi
2019-05-16 10:40       ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 3/9] [TODO] drm: rcar-du: Add basic support for CMM Jacopo Mondi
2019-05-11 18:45   ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 4/9] drm: rcar-du: kms: Create CMM instances Jacopo Mondi
2019-05-11 18:56   ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 5/9] drm: rcar-du: Add CMM support for M3-W Jacopo Mondi
2019-05-11 18:47   ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 6/9] drm: rcar-du: crtc: Setup the CMM Jacopo Mondi
2019-05-11 18:59   ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 7/9] drm: rcar-du: group: Enable CMM unit Jacopo Mondi
2019-05-11 19:02   ` Laurent Pinchart
2019-05-08 17:34 ` [RFC 8/9] clk: renesas: r8a7796: Add CMM clocks Jacopo Mondi
2019-05-09  9:12   ` Geert Uytterhoeven
2019-05-11 18:21   ` Laurent Pinchart
2019-05-21  8:47     ` Geert Uytterhoeven
2019-05-08 17:34 ` [RFC 9/9] arm64: dts: renesas: r8a7796: Add CMM units Jacopo Mondi
2019-05-11 18:25   ` Laurent Pinchart

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=CAMuHMdV3ar8JnPo0S-MEUgPdNSDp8jKG95Tq_483ydn0swZqqA@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=Harsha.ManjulaMallikarjun@in.bosch.com \
    --cc=VenkataRajesh.Kalakodima@in.bosch.com \
    --cc=jacopo+renesas@jmondi.org \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-renesas-soc@vger.kernel.org \
    /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).