From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758024AbdKOSj3 (ORCPT ); Wed, 15 Nov 2017 13:39:29 -0500 Received: from mail-qt0-f176.google.com ([209.85.216.176]:50073 "EHLO mail-qt0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752585AbdKOSjU (ORCPT ); Wed, 15 Nov 2017 13:39:20 -0500 X-Google-Smtp-Source: AGs4zMbg4q8d6h0hg/RUpMBNgMZhD8a0chKXdO3OEXTd1QkMnRHPEnOIZUBRsqpPQun8a6uqo119qmD9aiwRkUY1lak= MIME-Version: 1.0 In-Reply-To: <20171115181505.GB6736@w540> References: <1510743363-25798-1-git-send-email-jacopo+renesas@jmondi.org> <1510743363-25798-2-git-send-email-jacopo+renesas@jmondi.org> <20171115181505.GB6736@w540> From: Geert Uytterhoeven Date: Wed, 15 Nov 2017 19:39:18 +0100 X-Google-Sender-Auth: s5xq_c_ywhnE3MOUe2kHpxjppvk Message-ID: Subject: Re: [PATCH v1 01/10] dt-bindings: media: Add Renesas CEU bindings To: jacopo mondi Cc: Jacopo Mondi , Laurent Pinchart , Magnus Damm , Mauro Carvalho Chehab , Hans Verkuil , Linux-Renesas , Linux Media Mailing List , Linux-sh list , "linux-kernel@vger.kernel.org" , Rob Herring , Mark Rutland , "devicetree@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jacopo, On Wed, Nov 15, 2017 at 7:15 PM, jacopo mondi wrote: > On Wed, Nov 15, 2017 at 02:07:31PM +0100, Geert Uytterhoeven wrote: >> On Wed, Nov 15, 2017 at 11:55 AM, Jacopo Mondi >> wrote: >> > --- /dev/null >> > +++ b/Documentation/devicetree/bindings/media/renesas,ceu.txt >> > @@ -0,0 +1,87 @@ >> > +Renesas Capture Engine Unit (CEU) >> > +---------------------------------------------- >> > + >> > +The Capture Engine Unit is the image capture interface found on Renesas >> > +RZ chip series and on SH Mobile ones. >> > + >> > +The interface supports a single parallel input with up 8/16bits data bus width. >> >> ... with data bus widths up to 8/16 bits? >> >> > + >> > +Required properties: >> > +- compatible >> > + Must be "renesas,renesas-ceu". >> >> The double "renesas" part looks odd to me. What about "renesas,ceu"? > > I'm totally open for better "compatible" strings here, so yeah, let's > got for the shorter one you proposed... > >> Shouldn't you add SoC-specific compatible values like "renesas,r7s72100-ceu", >> too? > > Well, I actually have no SoC-specific data in the driver, so I don't > need SoC specific "compatible" values. But if it's a good practice > to have them anyway, I will add those in next spin.. You don't necessarily need them in the driver, but in the bindings and DTS, just in case a difference is discovered later. 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