From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: gregkh@linuxfoundation.org, andre.draszik@linaro.org,
linux@roeck-us.net, shufan_lee@richtek.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@collabora.com, pablo.sun@mediatek.com
Subject: Re: [PATCH v2] usb: typec: tcpci_rt1711h: Unmask alert interrupts to fix functionality
Date: Wed, 26 Feb 2025 12:04:44 +0200 [thread overview]
Message-ID: <Z77nPL_84FgjkDMX@kuha.fi.intel.com> (raw)
In-Reply-To: <20250219114700.41700-1-angelogioacchino.delregno@collabora.com>
On Wed, Feb 19, 2025 at 12:47:00PM +0100, AngeloGioacchino Del Regno wrote:
> During probe, the TCPC alert interrupts are getting masked to
> avoid unwanted interrupts during chip setup: this is ok to do
> but there is no unmasking happening at any later time, which
> means that the chip will not raise any interrupt, essentially
> making it not functional as, while internally it does perform
> all of the intended functions, it won't signal anything to the
> outside.
>
> Unmask the alert interrupts to fix functionality.
>
> Fixes: ce08eaeb6388 ("staging: typec: rt1711h typec chip driver")
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Shouldn't this go to the stable kernels as well?
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
>
> Changes in v2:
> - Moved interrupts enablement call to before enabling irq wakeup as
> enable_irq_wake() cannot fail, and if anything goes wrong, since the
> interrupt was previously requested with devm, no further action is
> needed. Thanks Greg!
>
> drivers/usb/typec/tcpm/tcpci_rt1711h.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/usb/typec/tcpm/tcpci_rt1711h.c b/drivers/usb/typec/tcpm/tcpci_rt1711h.c
> index 64f6dd0dc660..88c50b984e8a 100644
> --- a/drivers/usb/typec/tcpm/tcpci_rt1711h.c
> +++ b/drivers/usb/typec/tcpm/tcpci_rt1711h.c
> @@ -334,6 +334,11 @@ static int rt1711h_probe(struct i2c_client *client)
> {
> int ret;
> struct rt1711h_chip *chip;
> + const u16 alert_mask = TCPC_ALERT_TX_SUCCESS | TCPC_ALERT_TX_DISCARDED |
> + TCPC_ALERT_TX_FAILED | TCPC_ALERT_RX_HARD_RST |
> + TCPC_ALERT_RX_STATUS | TCPC_ALERT_POWER_STATUS |
> + TCPC_ALERT_CC_STATUS | TCPC_ALERT_RX_BUF_OVF |
> + TCPC_ALERT_FAULT;
>
> chip = devm_kzalloc(&client->dev, sizeof(*chip), GFP_KERNEL);
> if (!chip)
> @@ -382,6 +387,12 @@ static int rt1711h_probe(struct i2c_client *client)
> dev_name(chip->dev), chip);
> if (ret < 0)
> return ret;
> +
> + /* Enable alert interrupts */
> + ret = rt1711h_write16(chip, TCPC_ALERT_MASK, alert_mask);
> + if (ret < 0)
> + return ret;
> +
> enable_irq_wake(client->irq);
>
> return 0;
> --
> 2.48.1
--
heikki
prev parent reply other threads:[~2025-02-26 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:47 [PATCH v2] usb: typec: tcpci_rt1711h: Unmask alert interrupts to fix functionality AngeloGioacchino Del Regno
2025-02-26 10:04 ` Heikki Krogerus [this message]
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=Z77nPL_84FgjkDMX@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andre.draszik@linaro.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pablo.sun@mediatek.com \
--cc=shufan_lee@richtek.com \
/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;
as well as URLs for NNTP newsgroup(s).