Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp316152ybt; Sat, 13 Jun 2020 05:31:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyNjFhPrkOe0S69MO/qi4sXknumhxpmQtsIx4ZWkchj9vGNV+09k5UfqqkoS69YOX4Y3g2Q X-Received: by 2002:a17:906:4a03:: with SMTP id w3mr17318964eju.154.1592051484201; Sat, 13 Jun 2020 05:31:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592051484; cv=none; d=google.com; s=arc-20160816; b=dT0tOODphgQuFIgBUYexOuqQzrITiMoYweOLrjjtmDIL3XKYaPzS7kH1Izat8JbRrq 5QERR4o+xZjDebivKmHkTYgHhByTUMMhKQfVrrnMen49FzNJhSe6ZOEzy6mLJLq94ybH LoVzqWJXYOyXQ9RdKL7AM6cd+HZrsWWn1jZeMogt4G2KShu8prCZjbaPHia+QDEoGgJl yL6y0eCUEAx/Xgo2u8JopZqpBWAjV1fOMWRwo2p2+0REAifptY5ymkdj92QIbH6Jfe9+ ralHS+WGlGCd2H0nxfTtiWHpEZISQOrR5vDobG4f9Sqooh0PD2wjZyvU3DhngAFd1Zeq mldg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=ScB5b+83UlBd19JzdJhn2h6RXUIYr59XbHw5F51e4PM=; b=FH1MKbTdRaNjdyauZzBQd6onM8LhY7ePRHAZGte0U1nzdWhtT4VuuesvxmX+lgLUI9 Q46hPC3UwQEeVFn03CUycKscL26oOVNgW4VJqw38p8kQchdY8UI7F9Y/fvqTFu2D9o7l yCWVoiRa5sBcZ6d/bnAlHxLLutgZowkOpWlqk6zBl1XV3zlDSjxBkCQIR/xnBFu/Mvz/ gz9MP/gPBZxJEzlqaO9nU3rJ2XHM6k5u7NiDKqoqEVx1wKitW1CKsdkp90hC3AxIA1q8 0yxUFcGF0+ZW2nSzdcXu9evqew+rRQUpySzH1m4sZaWS49BXm5HA6/cfPli8bjjeU9fo DQPg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c11si5584058ejs.720.2020.06.13.05.31.01; Sat, 13 Jun 2020 05:31:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726329AbgFMM2v (ORCPT + 99 others); Sat, 13 Jun 2020 08:28:51 -0400 Received: from relay8-d.mail.gandi.net ([217.70.183.201]:37649 "EHLO relay8-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726021AbgFMM2u (ORCPT ); Sat, 13 Jun 2020 08:28:50 -0400 X-Originating-IP: 93.34.118.233 Received: from uno.localdomain (93-34-118-233.ip49.fastwebnet.it [93.34.118.233]) (Authenticated sender: jacopo@jmondi.org) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 0F0CB1BF204; Sat, 13 Jun 2020 12:28:43 +0000 (UTC) Date: Sat, 13 Jun 2020 14:32:07 +0200 From: Jacopo Mondi To: Rob Herring Cc: Kieran Bingham , Laurent Pinchart , linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, Hyun Kwon , linux-media@vger.kernel.org, Linus Walleij , Mauro Carvalho Chehab , Kieran Bingham , sakari.ailus@iki.fi, Niklas =?utf-8?Q?S=C3=B6derlund?= , Laurent Pinchart , Manivannan Sadhasivam , devicetree@vger.kernel.org, Niklas =?utf-8?Q?S=C3=B6derlund?= , linux-renesas-soc@vger.kernel.org, Rob Herring , Jacopo Mondi , Hans Verkuil Subject: Re: [PATCH v10 1/4] dt-bindings: media: i2c: Add bindings for Maxim Integrated MAX9286 Message-ID: <20200613123207.6ey6y5spfa5ajk4h@uno.localdomain> References: <20200612144713.502006-1-kieran.bingham+renesas@ideasonboard.com> <20200612144713.502006-2-kieran.bingham+renesas@ideasonboard.com> <20200612221003.GA3901624@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200612221003.GA3901624@bogus> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, On Fri, Jun 12, 2020 at 04:10:03PM -0600, Rob Herring wrote: > On Fri, 12 Jun 2020 15:47:10 +0100, Kieran Bingham wrote: > > From: Laurent Pinchart > > > > The MAX9286 deserializes video data received on up to 4 Gigabit > > Multimedia Serial Links (GMSL) and outputs them on a CSI-2 port using up > > to 4 data lanes. > > > > Signed-off-by: Laurent Pinchart > > Signed-off-by: Jacopo Mondi > > Signed-off-by: Kieran Bingham > > Reviewed-by: Niklas Söderlund > > Signed-off-by: Niklas Söderlund > > Reviewed-by: Rob Herring > > > > --- > > > > v7: > > - Collect Rob's RB tag > > - Remove redundant maxItems from remote-endpoints > > - Fix SPDX licence tag > > > > v10: > > [Jacopo] > > - Fix dt-validation > > - Fix dt-binding examples with 2 reg entries > > > > [Kieran] > > - Correctly match the hex camera node reg > > - Add (required) GPIO controller support > > > > .../bindings/media/i2c/maxim,max9286.yaml | 366 ++++++++++++++++++ > > 1 file changed, 366 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/media/i2c/maxim,max9286.yaml > > > > > My bot found errors running 'make dt_binding_check' on your patch: > > /builds/robherring/linux-dt-review/Documentation/devicetree/bindings/media/i2c/maxim,max9286.example.dt.yaml: example-0: i2c@e66d8000:reg:0: [0, 3865935872, 0, 64] is too long > > > See https://patchwork.ozlabs.org/patch/1308280 > > If you already ran 'make dt_binding_check' and didn't see the above > error(s), then make sure dt-schema is up to date: > > pip3 install git+https://github.com/devicetree-org/dt-schema.git@master --upgrade > I have updated my dt-schema installation to the latest github master ------------------------------------------------------------------------------- Successfully installed dtschema-2020.6.dev8+g4d2d86c https://github.com/devicetree-org/dt-schema/commit/4d2d86c5cd65cd3944ce0aaa400866bc36727bea $ /usr/bin/dt-validate -V 2020.6.dev8+g4d2d86c ------------------------------------------------------------------------------- But I still cannot reproduce the error. However, I see this commit in your next branch https://github.com/devicetree-org/dt-schema/commit/b72500282cfd2eba6f9df4d7553f696544b40ee6 "schemas: Add a schema to check 'reg' sizes " Which sounds very likely related to the above reported error. Was this intentional ? I'm not sure how I should handle this. The error reports the i2c node parents should have both address-cells and size-cells properties set to 2, but in the example there is not i2c node parent at all :) Should I add a parent node for the i2c in the example snippet ? Thanks j > Please check and re-submit. >