mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Piyush Mehta <piyush.mehta@amd.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"michal.simek@amd.com" <michal.simek@amd.com>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"git@amd.com" <git@amd.com>
Subject: Re: [PATCH] usb: dwc3: xilinx: add reset-controller support
Date: Thu, 12 Oct 2023 18:05:54 +0000	[thread overview]
Message-ID: <20231012180540.byvdiwtx7bgixidk@synopsys.com> (raw)
In-Reply-To: <20231005142215.1530-1-piyush.mehta@amd.com>

On Thu, Oct 05, 2023, Piyush Mehta wrote:
> Add a reset-controller for supporting Xilinx versal platforms. To reset
> the USB controller, get the reset ID from device-tree and using ID trigger
> the reset, with the assert and deassert reset controller APIs for USB
> controller initialization. Delay of microseconds is added in between assert
> and deassert to meet the setup and hold the time requirement of the reset.
> 
> Signed-off-by: Piyush Mehta <piyush.mehta@amd.com>
> ---
>  drivers/usb/dwc3/dwc3-xilinx.c | 17 ++++++++++-------
>  1 file changed, 10 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-xilinx.c b/drivers/usb/dwc3/dwc3-xilinx.c
> index 19307d24f3a0..d0780bf231fb 100644
> --- a/drivers/usb/dwc3/dwc3-xilinx.c
> +++ b/drivers/usb/dwc3/dwc3-xilinx.c
> @@ -32,9 +32,6 @@
>  #define XLNX_USB_TRAFFIC_ROUTE_CONFIG		0x005C
>  #define XLNX_USB_TRAFFIC_ROUTE_FPD		0x1
>  
> -/* Versal USB Reset ID */
> -#define VERSAL_USB_RESET_ID			0xC104036
> -
>  #define XLNX_USB_FPD_PIPE_CLK			0x7c
>  #define PIPE_CLK_DESELECT			1
>  #define PIPE_CLK_SELECT				0
> @@ -72,20 +69,26 @@ static void dwc3_xlnx_mask_phy_rst(struct dwc3_xlnx *priv_data, bool mask)
>  static int dwc3_xlnx_init_versal(struct dwc3_xlnx *priv_data)
>  {
>  	struct device		*dev = priv_data->dev;
> +	struct reset_control	*crst;
>  	int			ret;
>  
> +	crst = devm_reset_control_get_exclusive(dev, NULL);
> +	if (IS_ERR(crst))
> +		return dev_err_probe(dev, PTR_ERR(crst), "failed to get reset signal\n");
> +
>  	dwc3_xlnx_mask_phy_rst(priv_data, false);
>  
>  	/* Assert and De-assert reset */
> -	ret = zynqmp_pm_reset_assert(VERSAL_USB_RESET_ID,
> -				     PM_RESET_ACTION_ASSERT);
> +	ret = reset_control_assert(crst);
>  	if (ret < 0) {
>  		dev_err_probe(dev, ret, "failed to assert Reset\n");
>  		return ret;
>  	}
>  
> -	ret = zynqmp_pm_reset_assert(VERSAL_USB_RESET_ID,
> -				     PM_RESET_ACTION_RELEASE);
> +	/* reset hold time */
> +	usleep_range(5, 10);

Was this delay needed before? If so, is this a fix patch?

> +
> +	ret = reset_control_deassert(crst);
>  	if (ret < 0) {
>  		dev_err_probe(dev, ret, "failed to De-assert Reset\n");
>  		return ret;
> -- 
> 2.17.1
> 

BR,
Thinh

      reply	other threads:[~2023-10-12 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 14:22 Piyush Mehta
2023-10-12 18:05 ` Thinh Nguyen [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=20231012180540.byvdiwtx7bgixidk@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=git@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=p.zabel@pengutronix.de \
    --cc=piyush.mehta@amd.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

all inboxes | Powered by JetHome®