Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1707423pxb; Wed, 9 Feb 2022 02:45:26 -0800 (PST) X-Google-Smtp-Source: ABdhPJw3SIC5c6H/K/q6ZqVzr017gEDKeFqIu1ZfxwgDWwCHzuwtdgx7T8TRhv+nvHcg4Gt9KRta X-Received: by 2002:a17:902:e94e:: with SMTP id b14mr1800388pll.114.1644403526686; Wed, 09 Feb 2022 02:45:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644403526; cv=none; d=google.com; s=arc-20160816; b=t8dOMCRvd9NnLbQ7NTNOvmUIvJ2xiSCU6MnZlWiOMi7hnPtCGm7/VFcX77GggiouBa f0LbCQueyH+p82MnvfhoE1oJYqOMa3GrEIZLYOmS21t53KEkqDDAC6xHDk5zFj6MGCEi vHt9Un8wmchgoiqdSU6hQotOaT16n8bkPfgP8YkZ67FHhUyjVBoQml9WrcL/mzSeEhFV pLjungmWjG+B0TxONiHOGzl6wcwcWlDlfqQ1fn2GKBeXsQaNK9dLyc2fN+RUcNWmxJMb oXTni2tB1XzY0+32rBNxAXNudHdqtx4IMtBWZQ4jXVjo1RGI9XTeCTqPY2PuZ3LatXL7 bCZQ== 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=5++rdI0ZCWNhcJF9Ilqv0aOk35l2OcJh7Wbsyuqc6/E=; b=KJ8FMRQA3E2XhzhYTZf3JgX7h2JVp739OnBoAckSGKMZ/Sc3WzS+pc49Qn20PPfTUb SUjhuRN1m8pDJ2JB8/qdjmXRjfvlRAWtxNh3CtcTQiXRegqYUSP6GUxYRSEw4BdQrUXN pdRvBqmnGWWkc8jAiX7O5s8rQ3tjHBWsGkZoZT9249jsnlt0pM1t8hG6tkefBowdvdam Bhz8PGJSOHDWY7axx+nUIQ/iiF0nl9DWd/DkxHv9CQ51/notQ/NHPhIEuAx1YObmDBvM qisGHORyOhvu6Ss+rq5inZjjSYdavqG7YVLd3GO4J6hC00xmzyjsgsg0Dh2RLsyT0pKb eLvQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=tcDzdm4a; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id v12si13321688plg.294.2022.02.09.02.45.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 09 Feb 2022 02:45:26 -0800 (PST) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=tcDzdm4a; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 3F13BE0B2AB4; Wed, 9 Feb 2022 01:25:49 -0800 (PST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345484AbiBHFjv (ORCPT + 99 others); Tue, 8 Feb 2022 00:39:51 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43692 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347074AbiBHFjJ (ORCPT ); Tue, 8 Feb 2022 00:39:09 -0500 Received: from mail-pf1-x42e.google.com (mail-pf1-x42e.google.com [IPv6:2607:f8b0:4864:20::42e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89636C03FEE2 for ; Mon, 7 Feb 2022 21:35:34 -0800 (PST) Received: by mail-pf1-x42e.google.com with SMTP id v74so17002163pfc.1 for ; Mon, 07 Feb 2022 21:35:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=5++rdI0ZCWNhcJF9Ilqv0aOk35l2OcJh7Wbsyuqc6/E=; b=tcDzdm4a9mAzCZ2Y5FVfN7nHkgGzltgu/EMIfTzbrvddMVPWn/x84T/ysCG9mEZnGm BvNGlDvtRLYesNb+tVqpanRwatqOymYxEzChcUKNgrnAWX5FmfmLvwARnvJePwWkK7Cs xFk2lp92gZJ84ZKQQh3+0t46g8V9DLia9mj6W82NtDDqiTHTTJi1fzI1uj50QFlWQh5A 5nhuJs2NMJ1EquCy5B2kU6iK/ixMoiLl8WKX/ERWAlsLcR2abBpUNUrf9yM8VDMIQLtb i7xq1PB8oc2NSdD+yUnTTDBHO9XOtY7urxFxKu20yAgSQcJ4d2fS1EpQKluyNPnN76fc ct8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=5++rdI0ZCWNhcJF9Ilqv0aOk35l2OcJh7Wbsyuqc6/E=; b=kXGLefTmJjmU5+ioRBtJNa1V0beJelaxC1PufnF+EE2JnTwIvW6MfPlFhKVd6Px1U+ TSpMhErZvKes6OcdeVPUVVWFAcnTC/75gbE5Emx1Kf2n2VRmGnjKinLILjnm7rvtVZY/ k0RqkpoiB9Sh8zqjYiVG37oFJfxx5G+ocJuSMFK9qiMUAi+4q6+m4ROgsWmvQxPpL5x+ uv1/ZZYgI4IN/u1UxziWpicZCN0XbWOCLGYhK2EXALcOtKoRAUGooFuE59039ZDnWeMl READdk54WjahLwq96MTQXEM0H4Gjd1Fhm3EC66YlWyWbPyJxV05ifgaqJ0crGgxee9q+ gXrg== X-Gm-Message-State: AOAM532LnN3miY5o95R/dJG/CA47cTKuzvlm6STgVDbF1kMNC18TGumS 46baEyjs/G0fmhirrJ2TOkyx+A== X-Received: by 2002:aa7:828c:: with SMTP id s12mr453619pfm.6.1644298533822; Mon, 07 Feb 2022 21:35:33 -0800 (PST) Received: from google.com ([2401:fa00:1:10:4b6f:f14d:be50:86a]) by smtp.gmail.com with ESMTPSA id d22sm13850182pfl.71.2022.02.07.21.35.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 07 Feb 2022 21:35:33 -0800 (PST) Date: Tue, 8 Feb 2022 13:35:30 +0800 From: Tzung-Bi Shih To: Prashant Malani Cc: linux-kernel@vger.kernel.org, Benson Leung , "open list:CHROMEOS EC USB TYPE-C DRIVER" , Guenter Roeck Subject: Re: [PATCH 2/4] platform/chrome: cros_ec_typec: Get mux state inside configure_mux Message-ID: References: <20220207214026.1526151-1-pmalani@chromium.org> <20220207214026.1526151-3-pmalani@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220207214026.1526151-3-pmalani@chromium.org> X-Spam-Status: No, score=-9.5 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE, USER_IN_DEF_DKIM_WL autolearn=no 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 On Mon, Feb 07, 2022 at 09:40:26PM +0000, Prashant Malani wrote: > Move the function which gets current mux state inside the > cros_typec_configure_mux() function. It is better to group those > bits of functionality together, and it makes it easier to move around > cros_typec_configure_mux() later. nit: s/Move/Moves/. > static int cros_typec_configure_mux(struct cros_typec_data *typec, int port_num, > - uint8_t mux_flags, > struct ec_response_usb_pd_control_v2 *pd_ctrl) > { > struct cros_typec_port *port = typec->ports[port_num]; > + struct ec_response_usb_pd_mux_info mux_resp; > + struct ec_params_usb_pd_mux_info req = { > + .port = port_num, > + }; > struct ec_params_usb_pd_mux_ack mux_ack; > enum typec_orientation orientation; > int ret = 0; > > + ret = cros_ec_command(typec->ec, 0, EC_CMD_USB_PD_MUX_INFO, > + &req, sizeof(req), &mux_resp, sizeof(mux_resp)); It was `req` and `resp` in cros_typec_get_mux_info(). However, `mux_resp` for separating from `struct ec_response_usb_pd_control_v2 resp` in cros_typec_port_update(). It would be neat to be either {`req`, `resp`} or {`mux_req`, `mux_resp`} in cros_typec_configure_mux().