On Mon, May 28, 2018 at 10:52:41AM +0800, Li Jun wrote:
> From: Peter Chen <peter.c...@nxp.com>
> 
> With that we can clear any pending events and the port is registered
> so driver can be ready to handle typec events once we request irq.
> 
> Signed-off-by: Peter Chen <peter.c...@nxp.com>
> Signed-off-by: Li Jun <jun...@nxp.com>

FWIW:

Reviewed-by: Heikki Krogerus <heikki.kroge...@linux.intel.com>

> ---
>  drivers/staging/typec/tcpci.c | 15 +++++++++------
>  1 file changed, 9 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/typec/tcpci.c b/drivers/staging/typec/tcpci.c
> index b63f147..3b35fce 100644
> --- a/drivers/staging/typec/tcpci.c
> +++ b/drivers/staging/typec/tcpci.c
> @@ -537,24 +537,27 @@ static int tcpci_probe(struct i2c_client *client,
>       if (IS_ERR(chip->data.regmap))
>               return PTR_ERR(chip->data.regmap);
>  
> +     i2c_set_clientdata(client, chip);
> +
>       /* Disable chip interrupts before requesting irq */
>       err = regmap_raw_write(chip->data.regmap, TCPC_ALERT_MASK, &val,
>                              sizeof(u16));
>       if (err < 0)
>               return err;
>  
> +     chip->tcpci = tcpci_register_port(&client->dev, &chip->data);
> +     if (IS_ERR(chip->tcpci))
> +             return PTR_ERR(chip->tcpci);
> +
>       err = devm_request_threaded_irq(&client->dev, client->irq, NULL,
>                                       _tcpci_irq,
>                                       IRQF_ONESHOT | IRQF_TRIGGER_LOW,
>                                       dev_name(&client->dev), chip);
> -     if (err < 0)
> +     if (err < 0) {
> +             tcpci_unregister_port(chip->tcpci);
>               return err;
> +     }
>  
> -     chip->tcpci = tcpci_register_port(&client->dev, &chip->data);
> -     if (IS_ERR(chip->tcpci))
> -             return PTR_ERR(chip->tcpci);
> -
> -     i2c_set_clientdata(client, chip);
>       return 0;
>  }

Thanks,

-- 
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to