Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp700296imm; Fri, 22 Jun 2018 03:57:24 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKpCffzhT81LPgEc959LIJ/M3ztoLFth/kqt2/zZn1WehunW4qhSiyeFJDHBs/BTk0Ep+mL X-Received: by 2002:a65:5c03:: with SMTP id u3-v6mr920016pgr.402.1529665044858; Fri, 22 Jun 2018 03:57:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529665044; cv=none; d=google.com; s=arc-20160816; b=ZvHGQ7OX1IINN+QxB9pz4RD9TyDGs8w236XvLRCYJxoi2YlRloRQg1qIli8agciGGX VW9YOATVE68pLYhC3QbX827ZeN/spetZfq7Xar/Ihp8++hJS1WecU2GNCrblfvuDs5Wa v0hybGF8ipwZqdHbXyPJc2kYC2D//KXJbSqC5NJBdNrsLX5nt2bvoq1gZ94QHMMWNFh6 W1T/aGWAYOfNaeDHGyCgUf31+IM7znC4hkfEWdX/oXH/4zmZyVNj61La385BRXPiA0KL 5m9khiAqTDiobPUQp0LRcpoWknf0BeKpIASjyFJXKGgOKFasiWNfQtjurSAoCXDiXOCQ oVjg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=c8T00bYteRie5Za3pyNgLdpv1hkKAiRLVB04b5TAjig=; b=1HphCkX6soc/Ciu8bm3HhzVjBxmcFEsHd30LXZgXVX9N2ifSNs9Uo6NdZD8BQ5DV0X 3Z+jNY8JsJvLTSWGiilB1pWljPxkD+XMcHzremJ396WyCE1fmrTUTNIwsYqQ+ivJU4Qe iPcfHbxmNBpYMts2RO2uWH68VNJATjdfjJO+9+7HwxVBOIqSkRvd6SNytArr1xL7BOSP ZB/6v/q1StixSlEwmIYBvrvUCzDRTEh+M7TV6OuhhY3Y7zvzaZre2kxmdZEk+41n/MGw 2qjyX5oyswJrIXccz464TJzRuKqLfwL2FkacWtuxmg28IsBlasT52V0O69pRV18MKTrR xwxQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=1JNKWyZS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b23-v6si6973659pls.341.2018.06.22.03.57.10; Fri, 22 Jun 2018 03:57:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=1JNKWyZS; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933468AbeFVK4a (ORCPT + 99 others); Fri, 22 Jun 2018 06:56:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:56352 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751301AbeFVK42 (ORCPT ); Fri, 22 Jun 2018 06:56:28 -0400 Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com [74.125.82.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B77CC240C7; Fri, 22 Jun 2018 10:56:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1529664988; bh=ag6SOwZlLB7gU8RbUAokzJnFkn87+FoaMApvhMmj0vM=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=1JNKWyZS5aDaI1VahJZeSySMoBed9RnReeMDUkF9Gx/PbYjZkwmpDKOn93hhurp4Z Vd6J9Qf3PEe0dtBPlFbwQIseV1Kmb4Fap4SUR2RN3roczVJ6QoggggeyEVo/1fMkoH Y3ue81DsBEx0Y6qgw9H4P7pUj7cfpmoODGaF2Pbw= Received: by mail-wm0-f44.google.com with SMTP id r15-v6so1820051wmc.1; Fri, 22 Jun 2018 03:56:27 -0700 (PDT) X-Gm-Message-State: APt69E3Z2D0A1nDxeMcM7GAKR7WyQj3gzvHuFDfirSLcd1N8mTfn9tGh trF4NzrV0a0yDYlZeBTwYlMnS6JKKF5BKoS48KM= X-Received: by 2002:a1c:58d5:: with SMTP id m204-v6mr1263522wmb.118.1529664986307; Fri, 22 Jun 2018 03:56:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:9166:0:0:0:0:0 with HTTP; Fri, 22 Jun 2018 03:56:25 -0700 (PDT) In-Reply-To: <20180622103910eucas1p239a4f8545b3ef340fe5d0a8b954c48ac~6dUIg5f5F1882718827eucas1p2e@eucas1p2.samsung.com> References: <20180515121239.18192-1-a.hajda@samsung.com> <20180515121239.18192-3-a.hajda@samsung.com> <20180620182844.5nmlj5djbjgwy3wn@kozik-lap> <20180622103910eucas1p239a4f8545b3ef340fe5d0a8b954c48ac~6dUIg5f5F1882718827eucas1p2e@eucas1p2.samsung.com> From: Krzysztof Kozlowski Date: Fri, 22 Jun 2018 12:56:25 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 2/2] arm64: dts: exynos: add OF graph between USB-PHY and MUIC To: Andrzej Hajda Cc: "open list:DESIGNWARE USB3 DRD IP DRIVER" , Bartlomiej Zolnierkiewicz , Marek Szyprowski , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Felipe Balbi , Greg Kroah-Hartman , Inki Dae , Rob Herring , Mark Rutland , Chanwoo Choi , Laurent Pinchart , linux-kernel@vger.kernel.org, "linux-samsung-soc@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 22 June 2018 at 12:39, Andrzej Hajda wrote: > On 20.06.2018 20:28, Krzysztof Kozlowski wrote: >> On Tue, May 15, 2018 at 02:12:39PM +0200, Andrzej Hajda wrote: >>> OF graph describes USB data lanes between USB-PHY and respective MUIC. >>> Since graph is present and DWC driver can use it to get extcon, obsolete >>> extcon property can be removed. >>> >>> Signed-off-by: Andrzej Hajda >>> --- >>> .../dts/exynos/exynos5433-tm2-common.dtsi | 19 ++++++++++++++++++- >>> 1 file changed, 18 insertions(+), 1 deletion(-) >> dtc W=1 now complains with: >> === >> Warning (graph_child_address): >> /soc/hsi2c@14d90000/max77843@66/max77843-muic/ports: graph node has single child node 'port@0', #address-cells/#size-cells are not necessary >> === >> >> Do you plan to add more ports soon? > > There could be a link between UART and MUIC, it could be beneficial for > the platform - there is no point to feed UART with data when UART output > is muxed-out by MUIC. > So I plan to investigate it but this is not on my short list :) > Alternatively one can create graphs without using it atm. In that case could you remove here the address/size-cells to fix the warning? I see that code uses -1 in of_graph_get_remote_node() so it should not depend on the reg number. Best regards, Krzysztof