Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp131674pxb; Mon, 31 Jan 2022 17:18:18 -0800 (PST) X-Google-Smtp-Source: ABdhPJwP3QozIU2nGbZ9mpT2dTtPO80M+jyLf6/vmdJmx4JJIIazVkfVpLGKbOkJY0i9zmzXrTJY X-Received: by 2002:a05:6402:693:: with SMTP id f19mr23046968edy.1.1643678298679; Mon, 31 Jan 2022 17:18:18 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643678298; cv=none; d=google.com; s=arc-20160816; b=d/XbVs1EErR3b6lH0Jd8HQ2wcIYDigyS5eeSE8C6v6oHWjc1ghPX7IaUl2H0JgCydU Sv/KgEn8ZUk57gOM6Yq1j3hQrKSviNxvhbmU8OFO+QGnb8EKtTPuz8pVDd0Zdb3INDKw 0CTgqLn+UI/HYsFqgpjU/53slezGN74DfTYa1aMBbZvkRRC4Z1GldLYC48iQqeBoNj6F tM8oxRm27N2iqUajZ43fcOgk9iIJFnVd8JZQf/CbvCiJET/fkW3X7XZNznuV+z/Z7GQm fmOKriqPVGeYVwEyMHegPcyptTZSNdHkkUxIOLOxJ+fakpR/pciNz//s0VfBiAefhHEk UMrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=KVPWNoQrOh4gwIS/NTKfwX1pCCKtfusbVveEiycdTlA=; b=AhZ4ihnHQYTocFJhGZjQOktEWN70f6OGEp7UB8UV1eEyDuMZaCrYBVfNOG/c3NljxX XYV8SNkS5pmbdG6S/jDd3k0uHHOfOuSqsDNUdtKcgWbXPiHDbCpNaIY6WWxqmx7Wzs6Y ZUkpA7vKcYGN5Z3KXPuwm8Hjp7rps4Ma7kixrQ4cA6nRyocLsfh4fktUoed2E7LKjoTP h+Xl2x851KmhrjeamMrux4kcHB4oMmDFFT/1Yyr4yHqK+OkLDdubfGIoYPAh/We7aoQu m6KAlpU/UFIuf38XEOFG/5yJvJu5a4Y39W5RLUBtqumt6DBV2l1YRNqDNk7osY6dCVJM A3Qw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b="DMKpx/mO"; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ne13si8312764ejc.856.2022.01.31.17.17.54; Mon, 31 Jan 2022 17:18:18 -0800 (PST) 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=@gmail.com header.s=20210112 header.b="DMKpx/mO"; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232326AbiA2JXZ (ORCPT + 99 others); Sat, 29 Jan 2022 04:23:25 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42218 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232265AbiA2JXW (ORCPT ); Sat, 29 Jan 2022 04:23:22 -0500 Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 884DEC06173B; Sat, 29 Jan 2022 01:23:21 -0800 (PST) Received: by mail-lf1-x130.google.com with SMTP id a28so16502970lfl.7; Sat, 29 Jan 2022 01:23:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KVPWNoQrOh4gwIS/NTKfwX1pCCKtfusbVveEiycdTlA=; b=DMKpx/mOMfOI21feRiUbT2oeVdaTx0RfWxyiFQ2n5jAFIdjM+oaXTaAWOTF51h8lIt EfCy8DZfnipXO8aRfg0Mp/Y/DjwkUY3kjMzpyh3LhL7emtVBR7jykxnh9KuyyXu+IVzo +Uv+hRCF2HBbvSkvq1KbPU4KnQotY2tyU8EVZdjGW4vNrC/aXsFj8v4RKWA1bAAqY7/i V2GDPndsnk0wdqVwuogA7Uf8+TfDu7G4kdc3n4ksVQStfs7elj3cdb+Af92cwJuDqUCa E67uootxFouyYc2Y3LyprLnGvamc+q6i/Jx0IbmUFkmG+vGEWG4ZJBJSGSrxIRWng7kM 0gPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=KVPWNoQrOh4gwIS/NTKfwX1pCCKtfusbVveEiycdTlA=; b=Pduayh2X+wLC+1M0LO/qTliA5JVcxBzVQc2glsoUpQxxFUi2ziPkr3zeoHgrIT/cQH 6NqEtQ4TK75XOCH907C+Cm+1dxXv2WeSB3UkVwaPwSoHsfCtcHtphT7yDn89jeIZJSNB SI33fxvnS7BRytmU6bdVmRogmfGi7B9DJeUw3nv2a5BcRcdIdq0m9/1cnBSZGKWyIt6e 9PDwsnwn+yeTn352kf27/XX6RRnWHtYdzt5q9hxlEy5QwE+mMmG7Ui1xfLa7O9hb7RpQ s038DhrYYmqdUCqq/vEcdY9UTn7hPzuSAu7XNs3UXGWPxZ2ZaG79gPBX1mQRfYIWiAik nB4Q== X-Gm-Message-State: AOAM53328oqGAGrmWQeGqC1eXrwYBnF04Z3zvfu14B5wMdqEKaZSowGT cA3YHB6WuKF24TsA0YTk1l75GSpQHAcbsQ== X-Received: by 2002:a05:6512:33d1:: with SMTP id d17mr1232439lfg.455.1643448199773; Sat, 29 Jan 2022 01:23:19 -0800 (PST) Received: from smtpclient.apple (31-178-191-245.dynamic.chello.pl. [31.178.191.245]) by smtp.gmail.com with ESMTPSA id u15sm658935lfq.107.2022.01.29.01.23.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Jan 2022 01:23:19 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Subject: Re: [PATCH 1/2] arm64: dts: rockchip: rename and sort the rk356x usb2 phy handles From: Piotr Oniszczuk In-Reply-To: Date: Sat, 29 Jan 2022 10:23:18 +0100 Cc: "linux-arm-kernel@lists.infradead.org" , "open list:ARM/Rockchip SoC..." , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Rob Herring , Heiko Stuebner , Nicolas Frattaroli , Liang Chen Content-Transfer-Encoding: quoted-printable Message-Id: References: <20220127190456.2195527-1-michael.riesch@wolfvision.net> To: Peter Geis , Michael Riesch X-Mailer: Apple Mail (2.3654.120.0.1.13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >=20 > Good Evening, >=20 > While I'm not against this idea, my main concern still stands. > I spent a great deal of thought on this, and decided to go the route I > did to maintain consistency with previous generations. > As such, I see one of three paths here: > - Pull this patch only and depart rk356x from previous SoCs. > - Do the same for previous SoCs to maintain consistency. > - Drop this patch to maintain consistency with previous SoCs. >=20 > I ask that others weigh in here, as offline discussion has produced > mixed results already. just pure user perspective (who spent last weeks considerable time to develop DT for rk3566 tvbox. = 99% of my work was by reading/learning from other boards existing DT's. = Any inconsistencies in DTs makes work for such ppl like me much more = harder): For option 1 - i don't see value For option 2 - what is reward for extra work needs to be done on all = other SoCs? so option 3 seems to be natural choice... in other words: for me: option 1 brings practically zero value + increased inconsistency. option 2: extra work - but consistency is like in option 3 (so where is = value?) so option 3 offers the same consistency - but without extra work... =20 just my 0.02$ =20=