mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Enric Balletbo i Serra <enric.balletbo@collabora.com>
To: Prashant Malani <pmalani@chromium.org>, linux-kernel@vger.kernel.org
Cc: Benson Leung <bleung@chromium.org>, Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH 2/2] platform/chrome: cros_ec_typec: Use existing feature check
Date: Tue, 3 Aug 2021 12:09:47 +0200	[thread overview]
Message-ID: <81610a2b-aa3f-f8d7-5214-e59a7ce839d6@collabora.com> (raw)
In-Reply-To: <20210802184711.3872372-2-pmalani@chromium.org>

Hi Prashant,

Thank you for your patch.

On 2/8/21 20:47, Prashant Malani wrote:
> Replace the cros_typec_feature_supported() function with the
> pre-existing cros_ec_check_features() function which does the same
> thing.
> 
> Signed-off-by: Prashant Malani <pmalani@chromium.org>
> ---
>  drivers/platform/chrome/cros_ec_typec.c | 33 +++++++++----------------
>  1 file changed, 11 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/platform/chrome/cros_ec_typec.c b/drivers/platform/chrome/cros_ec_typec.c
> index 27c068c4c38d..f96af8aa31b5 100644
> --- a/drivers/platform/chrome/cros_ec_typec.c
> +++ b/drivers/platform/chrome/cros_ec_typec.c
> @@ -1054,24 +1054,6 @@ static int cros_typec_get_cmd_version(struct cros_typec_data *typec)
>  	return 0;
>  }
>  
> -/* Check the EC feature flags to see if TYPEC_* features are supported. */
> -static int cros_typec_feature_supported(struct cros_typec_data *typec, enum ec_feature_code feature)
> -{
> -	struct ec_response_get_features resp = {};
> -	int ret;
> -
> -	ret = cros_typec_ec_command(typec, 0, EC_CMD_GET_FEATURES, NULL, 0,
> -				    &resp, sizeof(resp));
> -	if (ret < 0) {
> -		dev_warn(typec->dev,
> -			 "Failed to get features, assuming typec feature=%d unsupported.\n",
> -			 feature);
> -		return 0;
> -	}
> -
> -	return resp.flags[feature / 32] & EC_FEATURE_MASK_1(feature);
> -}
> -
>  static void cros_typec_port_work(struct work_struct *work)
>  {
>  	struct cros_typec_data *typec = container_of(work, struct cros_typec_data, port_work);
> @@ -1113,6 +1095,7 @@ MODULE_DEVICE_TABLE(of, cros_typec_of_match);
>  
>  static int cros_typec_probe(struct platform_device *pdev)
>  {
> +	struct cros_ec_dev *ec_dev = NULL;
>  	struct device *dev = &pdev->dev;
>  	struct cros_typec_data *typec;
>  	struct ec_response_usb_pd_ports resp;
> @@ -1132,10 +1115,16 @@ static int cros_typec_probe(struct platform_device *pdev)
>  		return ret;
>  	}
>  
> -	typec->typec_cmd_supported = !!cros_typec_feature_supported(typec,
> -					EC_FEATURE_TYPEC_CMD);
> -	typec->needs_mux_ack = !!cros_typec_feature_supported(typec,
> -					EC_FEATURE_TYPEC_MUX_REQUIRE_AP_ACK);
> +	if (typec->ec->ec)

Is this check really needed. Can typec->ec->ec be NULL at this point?

> +		ec_dev = dev_get_drvdata(&typec->ec->ec->dev);
> +
> +	if (ec_dev) {

and this?

> +		typec->typec_cmd_supported = !!cros_ec_check_features(ec_dev, EC_FEATURE_TYPEC_CMD);
> +		typec->needs_mux_ack = !!cros_ec_check_features(ec_dev,
> +							EC_FEATURE_TYPEC_MUX_REQUIRE_AP_ACK);
> +	} else {

and this?

> +		dev_warn(dev, "Invalid cros_ec_dev pointer; feature flags not checked.\n");

Can't just be

		typec->typec_cmd_supported = !!cros_ec_check_features(ec_dev,
EC_FEATURE_TYPEC_CMD);
		typec->needs_mux_ack = !!cros_ec_check_features(ec_dev,
EC_FEATURE_TYPEC_MUX_REQUIRE_AP_ACK);

Thanks,
 Enric

> +	}
>  
>  	ret = cros_typec_ec_command(typec, 0, EC_CMD_USB_PD_PORTS, NULL, 0,
>  				    &resp, sizeof(resp));
> 

  reply	other threads:[~2021-08-03 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 18:47 [PATCH 1/2] platform/chrome: cros_ec_proto: Update " Prashant Malani
2021-08-02 18:47 ` [PATCH 2/2] platform/chrome: cros_ec_typec: Use existing " Prashant Malani
2021-08-03 10:09   ` Enric Balletbo i Serra [this message]
2021-08-03 17:29     ` Prashant Malani
2021-08-23 17:30 ` [PATCH 1/2] platform/chrome: cros_ec_proto: Update " Benson Leung

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81610a2b-aa3f-f8d7-5214-e59a7ce839d6@collabora.com \
    --to=enric.balletbo@collabora.com \
    --cc=bleung@chromium.org \
    --cc=groeck@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmalani@chromium.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®