Received: by 2002:a05:7412:d8a:b0:e2:908c:2ebd with SMTP id b10csp3618743rdg; Wed, 18 Oct 2023 00:11:38 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHevlXqXlmq7zvj0rPkFFrDDJX+xqpqGIsj0iwo6NczFG74lMsXxjoXm4kjWAXc5s0pYKDt X-Received: by 2002:a05:6a20:e10f:b0:175:5a14:51c0 with SMTP id kr15-20020a056a20e10f00b001755a1451c0mr5281189pzb.5.1697613097652; Wed, 18 Oct 2023 00:11:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1697613097; cv=none; d=google.com; s=arc-20160816; b=nN0TnnZpHKkOusPBgGRnjefnibsiwtfvBQi+KKOPuyHZmQ9ia4Yk/wHTFUQGS+H62S gJ+bDXcmlgGe4Rwng7x1ZNPIxDRQESHS+0UmQd0C+td2I6JkWUNttg9IkS2ko6BurZ36 g5D2BRGobADDygZWwiwKnsv9LeNmD6pcTiemSh1paER0VRPYma2XFpWzgiz3Sns1qlxr VM9Fo7uqA6AwSHmTiYi4/4c88XbLQS0nXM6gzfaQ7ICmTA+TTwYtf6T1GkwkGvQmIW6i Am7nk76M6Wrjy5wiWaCz9NfpHJu3mH4MmcXHWdi624XQ+W+Z2VQSFN1URpqGZE6+NWFf OSJQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=glryhaCVwRzlPHhOXAohd+NY8GMnZ6MKMmZm1EUi7R8=; fh=CqR7dT0tI34GF8DnH4YZFrUTbDXYzH2xu6nhkYvc6AU=; b=Ckxe8dA8pliuvugeRznuPcMm7VEanXx4lfzeO0laJXtDznldwBbB08B+m0c0p/3u+T QVhAzn2bggC6AqCyMG/FpO6xryJfgoTNHgu3c0nA7MsUSoPVOjeC5D0gOjmFfJE0HelI ZssIIMeUog+RPtjLdRDeBFXssjomushyAKVwERuhJ/BiCVdZ24gnIgW7AF3RD66U360U lfdKOy9hvSXjh3eMywUP4Fs0ASiLt8qY0TeFPlGX01Bo0Xyk1KIVzm2KEIN53fXwJqD8 L/VvsdvKnQ8uMFmXVmYoxdDL1cjovogXqqsjEehaOG+XgZ8y3g+rclgshI2uQkr17dxg OCiQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=j0ZfiF21; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id ca27-20020a056a02069b00b005a0110eb926si1720120pgb.593.2023.10.18.00.11.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Oct 2023 00:11:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=j0ZfiF21; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id 3EEAF812AD3C; Wed, 18 Oct 2023 00:11:31 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235116AbjJRHL1 (ORCPT + 99 others); Wed, 18 Oct 2023 03:11:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57468 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235131AbjJRHLO (ORCPT ); Wed, 18 Oct 2023 03:11:14 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4A0D91B4; Wed, 18 Oct 2023 00:10:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1697613054; x=1729149054; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=2f5KGCkoKZZ5JhVOJVIHD3+5S1y0Tlk1F+D7jYqUrJ8=; b=j0ZfiF21quykqhMxRY1qotzbhVjUK/Pak7HAsfBUlUIgNXsog+aOJZVJ 1ERkvQAv8v0LASphIxjpB80kc+oXJiameRed7GBDnU4AhXKUj2wAmfnik vp0RZ5hDXTemYAwLljaNxX2trdfnRqHI9ZOspcRFaQR1kwoUKE3HPasIO CICzL/bWjDfdPdCg8nPVoHSOuehDt7O+au8MQ2sv2PJT9C+vKznD7nMYh nizfXy7ODXvfE1vw6vaRBj2bMltXJt+Xywk5ahKdoHnEPL+3SiIwjUBws 4laElsV8poqIhLL65TDTbbfAB5PZnJzq2nIyngaUQzEWuw0vvJIWQUHR7 g==; X-IronPort-AV: E=McAfee;i="6600,9927,10866"; a="376326405" X-IronPort-AV: E=Sophos;i="6.03,234,1694761200"; d="scan'208";a="376326405" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Oct 2023 00:10:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10866"; a="785775403" X-IronPort-AV: E=Sophos;i="6.03,234,1694761200"; d="scan'208";a="785775403" Received: from kuha.fi.intel.com ([10.237.72.185]) by orsmga008.jf.intel.com with SMTP; 18 Oct 2023 00:10:48 -0700 Received: by kuha.fi.intel.com (sSMTP sendmail emulation); Wed, 18 Oct 2023 10:10:47 +0300 Date: Wed, 18 Oct 2023 10:10:47 +0300 From: Heikki Krogerus To: Luca Weiss Cc: Greg Kroah-Hartman , Neil Armstrong , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Bjorn Andersson , ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH 2/3] usb: typec: fsa4480: Add support to swap SBU orientation Message-ID: References: <20231013-fsa4480-swap-v1-0-b877f62046cc@fairphone.com> <20231013-fsa4480-swap-v1-2-b877f62046cc@fairphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Wed, 18 Oct 2023 00:11:31 -0700 (PDT) Hi Luca, > > Shouldn't you loop through the endpoints? In any case: > > > > ep = fwnode_graph_get_next_endpoint(dev_fwnode(&fsa->client->dev, NULL)); > > The docs only mention one endpoint so I'm assuming just next_endpoint is > fine? I'm mostly concerned about what we may have in the future. If one day you have more than the one connection in your graph, then you have to be able to identify the endpoint you are after. But that may not be a problem in this case (maybe that "data-lanes" device property can be used to identify the correct endpoint?). We can worry about it then when/if we ever have another endpoint to deal with. thanks, -- heikki