From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Reply-To: kieran.bingham+renesas@ideasonboard.com Subject: Re: [PATCH/RFC 2/2] arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses References: <1528984088-24801-1-git-send-email-geert+renesas@glider.be> <1528984088-24801-3-git-send-email-geert+renesas@glider.be> <20180626195747.GB30143@rob-hp-laptop> <20180627151030.o2peqxdnesni3wfi@verge.net.au> From: Kieran Bingham Message-ID: Date: Wed, 27 Jun 2018 17:45:34 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 7bit To: Geert Uytterhoeven , Simon Horman Cc: Rob Herring , Geert Uytterhoeven , Mark Rutland , Laurent Pinchart , Mauro Carvalho Chehab , Magnus Damm , Shawn Guo , Sascha Hauer , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Media Mailing List , Linux-Renesas List-ID: On 27/06/18 17:40, Geert Uytterhoeven wrote: > Hi Simon, > > On Wed, Jun 27, 2018 at 5:10 PM Simon Horman wrote: >> On Tue, Jun 26, 2018 at 01:57:47PM -0600, Rob Herring wrote: >>> On Thu, Jun 14, 2018 at 03:48:08PM +0200, Geert Uytterhoeven wrote: >>>> With recent dtc and W=1: >>>> >>>> ...salvator-x.dtb: Warning (graph_port): /soc/i2c@e66d8000/video-receiver@70/port@10: graph node unit address error, expected "a" >>>> ...salvator-x.dtb: Warning (graph_port): /soc/i2c@e66d8000/video-receiver@70/port@11: graph node unit address error, expected "b" >>>> >>>> Unit addresses are always hexadecimal (without prefix), while the bases >>>> of reg property values depend on their prefixes. >>>> >>>> Fixes: 908001d778eba06e ("arm64: dts: renesas: salvator-common: Add ADV7482 support") >>>> Signed-off-by: Geert Uytterhoeven >>>> --- >>>> arch/arm64/boot/dts/renesas/salvator-common.dtsi | 4 ++-- >>>> 1 file changed, 2 insertions(+), 2 deletions(-) >>> >>> Reviewed-by: Rob Herring >> >> Geert, shall I apply this? > > I'd say yes. Thanks! I'm happy to throw an Acked-by: Kieran Bingham on the patch - but I had a pending question regarding the reg = <10> part. Shouldn't the reg become hex "reg = <0xa>" to be consistent? Either way - if there's precedent - take that route and I'm happy. -- Regards Kieran > > Gr{oetje,eeting}s, > > Geert >