From: Guenter Roeck <linux@roeck-us.net>
To: Xu Yang <xu.yang_2@nxp.com>, heikki.krogerus@linux.intel.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-imx@nxp.com, jun.li@nxp.com
Subject: Re: [PATCH v2] usb: typec: tcpci: Request IRQ with IRQF_SHARED
Date: Wed, 14 Dec 2022 09:04:44 -0800 [thread overview]
Message-ID: <218dbd73-d2fc-c316-ee02-43a462268f2b@roeck-us.net> (raw)
In-Reply-To: <20221214022334.2520677-1-xu.yang_2@nxp.com>
On 12/13/22 18:23, Xu Yang wrote:
> Under resource constraints, this interrupt may use other interrupt line
> or this interrupt line may be shared with other devices as long as they
> meet the sharing requirements. Besides, This irq flag will not cause other
> side effect if tcpci driver is the only user.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
Note: I initially thought that introducing alert_mask is overkill, but
the tcpci specification suggests that alert bits may be set even for
alerts disabled with the alert mask. So this code is ultimately simpler
than trying to determine in the interrupt handler which bits are actually
set in the alert mask.
Thanks,
Guenter
>
> ---
> Changes since v1:
> - return IRQ_NONE if the interrupt doesn't belong to this device
> ---
> drivers/usb/typec/tcpm/tcpci.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/usb/typec/tcpm/tcpci.c b/drivers/usb/typec/tcpm/tcpci.c
> index fe781a38dc82..c7796511695d 100644
> --- a/drivers/usb/typec/tcpm/tcpci.c
> +++ b/drivers/usb/typec/tcpm/tcpci.c
> @@ -33,6 +33,7 @@ struct tcpci {
> struct tcpm_port *port;
>
> struct regmap *regmap;
> + unsigned int alert_mask;
>
> bool controls_vbus;
>
> @@ -632,6 +633,9 @@ static int tcpci_init(struct tcpc_dev *tcpc)
> if (ret < 0)
> return ret;
> }
> +
> + tcpci->alert_mask = reg;
> +
> return tcpci_write16(tcpci, TCPC_ALERT_MASK, reg);
> }
>
> @@ -715,7 +719,7 @@ irqreturn_t tcpci_irq(struct tcpci *tcpci)
> else if (status & TCPC_ALERT_TX_FAILED)
> tcpm_pd_transmit_complete(tcpci->port, TCPC_TX_FAILED);
>
> - return IRQ_HANDLED;
> + return IRQ_RETVAL(status & tcpci->alert_mask); > }
> EXPORT_SYMBOL_GPL(tcpci_irq);
>
> @@ -838,7 +842,7 @@ static int tcpci_probe(struct i2c_client *client)
>
> err = devm_request_threaded_irq(&client->dev, client->irq, NULL,
> _tcpci_irq,
> - IRQF_ONESHOT | IRQF_TRIGGER_LOW,
> + IRQF_SHARED | IRQF_ONESHOT | IRQF_TRIGGER_LOW,
> dev_name(&client->dev), chip);
> if (err < 0) {
> tcpci_unregister_port(chip->tcpci);
next prev parent reply other threads:[~2022-12-14 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 2:23 [PATCH v2] usb: typec: tcpci: Request IRQ with IRQF_SHARED Xu Yang
2022-12-14 17:04 ` Guenter Roeck [this message]
2023-01-02 9:36 ` Heikki Krogerus
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=218dbd73-d2fc-c316-ee02-43a462268f2b@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jun.li@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=xu.yang_2@nxp.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