From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Martin Kepplinger <martin.kepplinger@puri.sm>
Cc: gregkh@linuxfoundation.org, sven@svenpeter.dev,
hdegoede@redhat.com, marcan@marcan.st, kernel@puri.sm,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] usb: typec: tipd: keep default interrupts enabled during probe()
Date: Tue, 11 Jan 2022 11:11:55 +0200 [thread overview]
Message-ID: <Yd1J2w0RCOOaG4Ku@kuha.fi.intel.com> (raw)
In-Reply-To: <20220110163559.711404-1-martin.kepplinger@puri.sm>
Hi Martin,
On Mon, Jan 10, 2022 at 05:35:59PM +0100, Martin Kepplinger wrote:
> Commit 9990f2f6264c ("usb: typec: tipd: Enable event interrupts by default")
> writes a fixed set of interrupts to TPS_REG_INT_MASK1. In case interrupts
> had been enabled by the firmware by default, these get disabled now
> which can break use cases. Only append to what is already enabled instead.
No, we have to know what are the interrupts that are actually needed.
Commmit 9990f2f6264c fixed an interrupt flood issue that was seen on
some platforms where the firmware I guess enabled absolutely
everything. This would just revert that.
So only enable the interrupts that you know you need.
> Fixes: 9990f2f6264c ("usb: typec: tipd: Enable event interrupts by default")
What is this fixing? What are the use cases you are talking about?
> Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
> ---
> drivers/usb/typec/tipd/core.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/typec/tipd/core.c b/drivers/usb/typec/tipd/core.c
> index 6d27a5b5e3ca..365ee5494c15 100644
> --- a/drivers/usb/typec/tipd/core.c
> +++ b/drivers/usb/typec/tipd/core.c
> @@ -744,10 +744,14 @@ static int tps6598x_probe(struct i2c_client *client)
>
> irq_handler = cd321x_interrupt;
> } else {
> + ret = tps6598x_read64(tps, TPS_REG_INT_MASK1, &mask1);
> + if (ret)
> + return ret;
> +
> /* Enable power status, data status and plug event interrupts */
> - mask1 = TPS_REG_INT_POWER_STATUS_UPDATE |
> - TPS_REG_INT_DATA_STATUS_UPDATE |
> - TPS_REG_INT_PLUG_EVENT;
> + mask1 |= TPS_REG_INT_POWER_STATUS_UPDATE |
> + TPS_REG_INT_DATA_STATUS_UPDATE |
> + TPS_REG_INT_PLUG_EVENT;
> }
>
> /* Make sure the controller has application firmware running */
thanks,
--
heikki
next prev parent reply other threads:[~2022-01-11 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 16:35 Martin Kepplinger
2022-01-11 9:11 ` Heikki Krogerus [this message]
2022-01-11 11:10 ` Hector Martin
2022-01-13 9:15 ` Martin Kepplinger
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=Yd1J2w0RCOOaG4Ku@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=kernel@puri.sm \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=martin.kepplinger@puri.sm \
--cc=sven@svenpeter.dev \
/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
Powered by JetHome