From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B5626C433F5 for ; Wed, 22 Sep 2021 06:44:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9153C611B0 for ; Wed, 22 Sep 2021 06:44:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232798AbhIVGpj (ORCPT ); Wed, 22 Sep 2021 02:45:39 -0400 Received: from mail-vs1-f53.google.com ([209.85.217.53]:41691 "EHLO mail-vs1-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232770AbhIVGpi (ORCPT ); Wed, 22 Sep 2021 02:45:38 -0400 Received: by mail-vs1-f53.google.com with SMTP id az15so1883435vsb.8; Tue, 21 Sep 2021 23:44:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=i2pUM5brNJqaej4iEqyIsIxjV6XIoFcwAAQ7Oqy6DEk=; b=zZ/VjtNJmEGWGWzWXntVXzcPdRka/SRQ8VwsH8haHFjnquiVTr2cnYccpNvUnsV7GC gE7kqMmF5O6s5Ke7mUKrT+MbzLGCuBKlZNH/CU327Q7vBEIPIQzXNO7JvlE1dSTVayx+ 287Xt/d7v0d7wgi1cd9GA/GWeO6LX8sFLUB4E/SkaezWUDKoF/kOSpoff9fjaHqNeQYM JlMVH6S3o5l287tQBeMwoXKBIT9T/ha6OxIdAJ/PxHoQsSuXsQl/NO7h9qAvspgyNOT5 e38DvsccFz+5rSCHUPer6MdAusR++HnYiSoDV7dh63m3DKunLcoU1gBfI8F9QoD38YCE qMfQ== X-Gm-Message-State: AOAM530R8JIQx/8VxiVvki8tmPRcymyNmATx/ZfDQy/kedglI2iLSklo M2SJToxl03VcnMFimrSHNIasDq0wJrEIDuB+XXyTzvw+ X-Google-Smtp-Source: ABdhPJwKxJBZAXv/SC7mdaGufQfqAQXm0UqBb5rpyK8VQIckPSoy5NjMixQOSxEm1nfiSw2knEhc9WDFntv0vlUHgXM= X-Received: by 2002:a67:cc1c:: with SMTP id q28mr23885496vsl.37.1632293048964; Tue, 21 Sep 2021 23:44:08 -0700 (PDT) MIME-Version: 1.0 References: <20210623135639.17125-1-laurent.pinchart+renesas@ideasonboard.com> In-Reply-To: From: Geert Uytterhoeven Date: Wed, 22 Sep 2021 08:43:57 +0200 Message-ID: Subject: Re: [RESEND] [PATCH v2 1/2] dt-bindings: display: bridge: Add binding for R-Car MIPI DSI/CSI-2 TX To: Laurent Pinchart Cc: DRI Development , Linux-Renesas , Rob Herring , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org Hi Laurent, On Wed, Sep 22, 2021 at 3:27 AM Laurent Pinchart wrote: > On Tue, Sep 21, 2021 at 05:53:52PM +0200, Geert Uytterhoeven wrote: > > On Wed, Jul 28, 2021 at 6:26 PM Laurent Pinchart wrote: > > > The R-Car MIPI DSI/CSI-2 TX is embedded in the Renesas R-Car V3U SoC. It > > > can operate in either DSI or CSI-2 mode, with up to four data lanes. > > > > > > Signed-off-by: Laurent Pinchart > > > Reviewed-by: Kieran Bingham > > > > Thanks for your patch! > > > > > --- /dev/null > > > +++ b/Documentation/devicetree/bindings/display/bridge/renesas,dsi-csi2-tx.yaml > > > @@ -0,0 +1,118 @@ > > > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > > > +%YAML 1.2 > > > +--- > > > +$id: http://devicetree.org/schemas/display/bridge/renesas,dsi-csi2-tx.yaml# > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > + > > > +title: Renesas R-Car MIPI DSI/CSI-2 Encoder > > > + > > > +maintainers: > > > + - Laurent Pinchart > > > + > > > +description: | > > > + This binding describes the MIPI DSI/CSI-2 encoder embedded in the Renesas > > > + R-Car V3U SoC. The encoder can operate in either DSI or CSI-2 mode, with up > > > + to four data lanes. > > > + > > > +properties: > > > + compatible: > > > + enum: > > > + - renesas,r8a779a0-dsi-csi2-tx # for V3U > > > + > > > + reg: > > > + maxItems: 1 > > > + > > > + clocks: > > > + items: > > > + - description: Functional clock > > > + - description: DSI (and CSI-2) functional clock > > > + - description: PLL reference clock > > > + > > > + clock-names: > > > + items: > > > + - const: fck > > > + - const: dsi > > > + - const: pll > > > > No interrupts? > > The hardware manual says there are 9 interrupts. > > Who comes up with such insanely high numbers of interrupts ? :-) > > What the hardware manual doesn't document is how interrupts are mapped. > There's indeed 9 of them, and there are 9 interrupt sources, but that's > all we know. I can easily add a > > interrupts: > maxItems: 9 > > but I can add interrupt names without additional information. It may be > possible to deduce some of the interrupt mappings from experiments, but > not all of them. What do you think would be a good way forward ? Leave > the interrupts out for now as we don't have the information ? Only list > the interrupts but not their names ? Something else ? I think what we did in the past is not list the interrupts at all. They can be added once we receive more documentation. 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