Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp627549pxv; Thu, 1 Jul 2021 06:04:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw/XASx/fYKpWpIj6Y88jVi85F9oYbU3OZHctwiDdY6MfNnVI2r/ZchEwbfqDulq/4vjE+s X-Received: by 2002:a17:907:1b11:: with SMTP id mp17mr41301502ejc.1.1625144641985; Thu, 01 Jul 2021 06:04:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625144641; cv=none; d=google.com; s=arc-20160816; b=R1ko9MHjtqog82hO+MI06dKpFLRfLTgLoCLouHZE/KZB4VHxEv7MCcEeBldfLHCEpa 9EjCPT2PCeiCaEFfomEk7cUvOl2rPI6SodpuM99wPvM9rMsb1DavMTLchEqrgrqdA1yc H94Uo1aygG0ETOYkkLuxy43vtRnQIuDVbEZkLfFks/IeiA5LdcD/8qet0bSRWCdd0aWv /DQQeP55/FFCXxcT2WFTyU+YNPc41RauHg+5JOcHQXxhvuY8cF8VlttKb1WqFmB8cKYp /02yeWDl1IS5fAk4tsWTIJj4svQzhOXzYf86dhBYu2s1uVq71azIVWZV3TJloF6YrDVr iG/A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=1gyaxxwYOZpXLqVnHi4CE3c1kMcas4IfjUJUZzaROx0=; b=tlvse8+ONYlcfMLS2w36TGr0XAJiNdxQTSsVt9dow05Vg3wKotaUUp5Ag+EgrUbABV Z4T4Aj2d7j8o/LHiL9KW3WO0oduVOa5vRNNlS50Q0ftweMZBsIGhsrDZrdLhztTEIsCW MrmUimgH/XeYn9obmBJrClMalkCUWwnx7WF6HA6XlsP/Or3uqqM533dbGckPGEqtBh3U 4FQ8LXhq2EtraKGBxlu2kqOCjAaktfZe8fpOnab/uN84g+1qp+CYa2RDeBhLK4LemlsX ldKYU75u4VzP8wPNSRpTLDkK0jqT8ss+NOIPrUo+hH3E+kPvQJNX6Kk7Zxsh8a158Xp8 Hh8w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="R5e6kah/"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bd1si14627718edb.60.2021.07.01.06.03.38; Thu, 01 Jul 2021 06:04:01 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="R5e6kah/"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236606AbhGANDX (ORCPT + 99 others); Thu, 1 Jul 2021 09:03:23 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:47765 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236638AbhGANDE (ORCPT ); Thu, 1 Jul 2021 09:03:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1625144400; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=1gyaxxwYOZpXLqVnHi4CE3c1kMcas4IfjUJUZzaROx0=; b=R5e6kah/pn7r8mlSHfs5nDnIGKO1wteMZMekDCUedheHpMB4hEzi/8lO09PmBddYTn+H5o 6z/B2POeWIODZZ0A+rsLPKUj166cyDW1QLXtkRYp2FqaeJYdZkvqdvE+0RNguFCCLb6OLd 8TpGusL66b1YXqnY6b3tSkV98ds9hYU= Received: from mail-io1-f70.google.com (mail-io1-f70.google.com [209.85.166.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-106-15pMqL4-M8e1IxdW0JNg0w-1; Thu, 01 Jul 2021 08:59:59 -0400 X-MC-Unique: 15pMqL4-M8e1IxdW0JNg0w-1 Received: by mail-io1-f70.google.com with SMTP id p19-20020a5d8b930000b02904a03acf5d82so4354713iol.23 for ; Thu, 01 Jul 2021 05:59:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=1gyaxxwYOZpXLqVnHi4CE3c1kMcas4IfjUJUZzaROx0=; b=nS62vtUHstSDNpcvYAa49mTNDJSABIEEr3RGjhPQDsW8NdmT5MI648mQSPntXhJp/4 GAymEFyZn44y5oeZN3whKEIPFDLriGdyC7SPn4k/hPEOa51ZcGTCCHPC0kPDPVOd7tam 5RjhmfyE+qaMCFlWKU7dD3+yQton7QKorARACnaulaalg0s2zoiHVyJH2Zz2GdJbNayS M0JTASNKhU4mm5GzK+/E3DhPwAEX8m0wubEsQVjuZmwhfnz9Pre7Yt/COVz8c9I0jgeG 2ex1HFyNh+f5UKXMhVVfc+eAaeI3dsQxYu4Te9l+cXbrsJTsE09F5RVau5lkev5GapOf exrw== X-Gm-Message-State: AOAM530nEFIe9wMcOIg0+f1MkrbypTb3yBJgFt//cvYGEWyaWConKJOn e7lKzdgI6bj5wMrzWGQHzLBo8FJB9Cp+V1abkV0ejBgjixvpe7o9XFivTP0xFPGj4ye4OTRLFk/ 0dJJzON7nKmlSIK2MMBrrzxYB X-Received: by 2002:a92:c792:: with SMTP id c18mr28985877ilk.75.1625144398941; Thu, 01 Jul 2021 05:59:58 -0700 (PDT) X-Received: by 2002:a92:c792:: with SMTP id c18mr28985856ilk.75.1625144398676; Thu, 01 Jul 2021 05:59:58 -0700 (PDT) Received: from kasuf.ausil.us (207-179-239-100.mtco.com. [207.179.239.100]) by smtp.gmail.com with ESMTPSA id l26sm13450699iok.26.2021.07.01.05.59.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Jul 2021 05:59:58 -0700 (PDT) Message-ID: Subject: Re: [PATCH 1/4] arm64: dts: rockchip: helios64: fixup USB setup From: Dennis Gilmore To: Uwe =?ISO-8859-1?Q?Kleine-K=F6nig?= , linux-rockchip@lists.infradead.org Cc: Rob Herring , Heiko Stuebner , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "moderated list:ARM/Rockchip SoC support" , open list Date: Thu, 01 Jul 2021 07:59:42 -0500 In-Reply-To: <01f1b032-14a8-a6fa-9063-23de65fc6f43@kleine-koenig.org> References: <20210701004043.18585-1-dgilmore@redhat.com> <01f1b032-14a8-a6fa-9063-23de65fc6f43@kleine-koenig.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.2 (3.40.2-1.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2021-07-01 at 11:31 +0200, Uwe Kleine-König wrote: > Hello, > > On 7/1/21 2:40 AM, Dennis Gilmore wrote: > > Without the usbdrd_dwc3_1 node defined u-boot will throw an error > > and > > reset the system. > > I wonder if this should better be fixed in u-boot then?! > > > All other rk3399 systems use this format > > This is true for the dwc nodes, however for the usb2 nodes there are > several that use this idiom (and even repeat the label name), see for > example the &u2phy0 node in > arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dtsi . > looking at that file is where I got the idea to set it up as I have proposed, it follows the format I have submitted Dennis > In my eyes it's a bit ugly to have the two nodes as separate entities > and on the same indentation level in the machine dts given that one > is > the parent of the other and enabling USB needs both status settings. > > Best regards > Uwe >