mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Angus Ainslie (Purism)" <angus@akkea.ca>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] usb: typec: tcpci: add functions to read the VBUS voltage
Date: Tue, 7 May 2019 18:59:36 -0700	[thread overview]
Message-ID: <f70df755-9462-54af-cd7d-83d35c1dd3f8@roeck-us.net> (raw)
In-Reply-To: <20190508004027.16558-2-angus@akkea.ca>

On 5/7/19 5:40 PM, Angus Ainslie (Purism) wrote:
> Show an error when the VBUS voltage is out of range.
> 
> Signed-off-by: Angus Ainslie (Purism) <angus@akkea.ca>
> ---
>   drivers/usb/typec/tcpm/tcpci.c | 35 ++++++++++++++++++++++++++++++++++
>   1 file changed, 35 insertions(+)
> 
> diff --git a/drivers/usb/typec/tcpm/tcpci.c b/drivers/usb/typec/tcpm/tcpci.c
> index a5746657b190..223941e11ef3 100644
> --- a/drivers/usb/typec/tcpm/tcpci.c
> +++ b/drivers/usb/typec/tcpm/tcpci.c
> @@ -261,6 +261,26 @@ static int tcpci_set_pd_rx(struct tcpc_dev *tcpc, bool enable)
>   	return 0;
>   }
>   
> +static int tcpci_get_vbus_voltage(struct tcpc_dev *tcpc)
> +{
> +	struct tcpci *tcpci = tcpc_to_tcpci(tcpc);
> +	u16 vbus_reg;
> +	unsigned int vbus_voltage;
> +	int ret, scale;
> +
> +	ret = tcpci_read16(tcpci, TCPC_VBUS_VOLTAGE, &vbus_reg);
> +	if (ret < 0)
> +		return ret;
> +
> +	vbus_voltage = vbus_reg & 0x3f;
> +
> +	scale = (vbus_reg >> 10) & 3;
> +	if (scale == 3)
> +		return -EIO;
> +
> +	return (vbus_voltage << scale) * 25;
> +}
> +
>   static int tcpci_get_vbus(struct tcpc_dev *tcpc)
>   {
>   	struct tcpci *tcpci = tcpc_to_tcpci(tcpc);
> @@ -401,6 +421,7 @@ static int tcpci_init(struct tcpc_dev *tcpc)
>   irqreturn_t tcpci_irq(struct tcpci *tcpci)
>   {
>   	u16 status;
> +	int ret;
>   
>   	tcpci_read16(tcpci, TCPC_ALERT, &status);
>   
> @@ -474,6 +495,20 @@ irqreturn_t tcpci_irq(struct tcpci *tcpci)
>   		tcpci_write16(tcpci, TCPC_FAULT_STATUS, fault_status);
>   	}
>   
> +	if (status & (TCPC_ALERT_V_ALARM_LO | TCPC_ALERT_V_ALARM_HI)) {
> +		ret = tcpci_get_vbus_voltage(&tcpci->tcpc);
> +
Extra empty line.

> +		if (ret >= 0) {
> +			if (status & TCPC_ALERT_V_ALARM_LO)
> +				dev_err(tcpci->dev, "Low VBUS voltage %d mV\n",
> +						ret);
> +
> +			if (status & TCPC_ALERT_V_ALARM_HI)
> +				dev_err(tcpci->dev, "High VBUS voltage %d mV\n",
> +						ret);
> +		}

This doesn't report anything if reading the VBUS voltage
returns an error.

Also, per TCPCI specification, you probably want to check
POWER_CONTROL.VBUS_VOLTAGE Monitor to see if it is enabled
in the first place.

On a higher level, the driver doesn't currently set limits for low
and high voltage alarms, and it doesn't enable those alarms. As such,
I wonder if/how you can get those alerts. Can you clarify ?

Thanks,
Guenter

> +	}
> +
>   	return IRQ_HANDLED;
>   }
>   EXPORT_SYMBOL_GPL(tcpci_irq);
> 


  reply	other threads:[~2019-05-08  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  0:40 [PATCH 0/1] usb: typec: tcpci: read the VBUS_VOLTAGE register Angus Ainslie (Purism)
2019-05-08  0:40 ` [PATCH 1/1] usb: typec: tcpci: add functions to read the VBUS voltage Angus Ainslie (Purism)
2019-05-08  1:59   ` Guenter Roeck [this message]
2019-05-08  1:47 ` [PATCH 0/1] usb: typec: tcpci: read the VBUS_VOLTAGE register Guenter Roeck

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=f70df755-9462-54af-cd7d-83d35c1dd3f8@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=angus@akkea.ca \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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®