Received-SPF: pass (google.com: domain of linux-kernel+bounces-20445-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Tue, 9 Jan 2024 08:12:58 +0100
From: Greg KH <gregkh@linuxfoundation.org>
To: Elad Nachman <enachman@marvell.com>
Cc: stern@rowland.harvard.edu, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: host: Add ac5 to EHCI Orion
Message-ID: <2024010943-deluxe-snitch-febc@gregkh>
References: <20240108175457.4113480-1-enachman@marvell.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20240108175457.4113480-1-enachman@marvell.com>

On Mon, Jan 08, 2024 at 07:54:57PM +0200, Elad Nachman wrote:
> From: Elad Nachman <enachman@marvell.com>
> 
> Add support for ac5 to the EHCI Orion platform driver.
> The ac5 SOC has DDR starting at offset 0x2_0000_0000,
> Hence it requires a larger than 32-bit DMA mask to operate.
> Move the dma mask to be pointed by the OF match data, and
> use that match data when initializng the DMA mask.
> 
> Signed-off-by: Elad Nachman <enachman@marvell.com>
> ---
>  drivers/usb/host/ehci-orion.c | 19 +++++++++++++++----
>  1 file changed, 15 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/usb/host/ehci-orion.c b/drivers/usb/host/ehci-orion.c
> index 6c47ab0a491d..58883664c884 100644
> --- a/drivers/usb/host/ehci-orion.c
> +++ b/drivers/usb/host/ehci-orion.c
> @@ -65,6 +65,15 @@ struct orion_ehci_hcd {
>  
>  static struct hc_driver __read_mostly ehci_orion_hc_driver;
>  
> +/*
> + * Legacy DMA mask is 32 bit.
> + * AC5 has the DDR starting at 8GB, hence it requires
> + * a larger (34-bit) DMA mask, in order for DMA allocations
> + * to succeed:
> + */
> +static const u64 dma_mask_orion =	DMA_BIT_MASK(32);
> +static const u64 dma_mask_ac5 =		DMA_BIT_MASK(34);
> +
>  /*
>   * Implement Orion USB controller specification guidelines
>   */
> @@ -211,6 +220,7 @@ static int ehci_orion_drv_probe(struct platform_device *pdev)
>  	int irq, err;
>  	enum orion_ehci_phy_ver phy_version;
>  	struct orion_ehci_hcd *priv;
> +	u64 *dma_mask_ptr;
>  
>  	if (usb_disabled())
>  		return -ENODEV;
> @@ -228,7 +238,8 @@ static int ehci_orion_drv_probe(struct platform_device *pdev)
>  	 * set. Since shared usb code relies on it, set it here for
>  	 * now. Once we have dma capability bindings this can go away.
>  	 */
> -	err = dma_coerce_mask_and_coherent(&pdev->dev, DMA_BIT_MASK(32));
> +	dma_mask_ptr = (u64 *)of_device_get_match_data(&pdev->dev);
> +	err = dma_coerce_mask_and_coherent(&pdev->dev, *dma_mask_ptr);
>  	if (err)
>  		goto err;
>  
> @@ -332,9 +343,9 @@ static void ehci_orion_drv_remove(struct platform_device *pdev)
>  }
>  
>  static const struct of_device_id ehci_orion_dt_ids[] = {
> -	{ .compatible = "marvell,orion-ehci", },
> -	{ .compatible = "marvell,armada-3700-ehci", },
> -	{},
> +	{ .compatible = "marvell,orion-ehci", .data = &dma_mask_orion},
> +	{ .compatible = "marvell,armada-3700-ehci", .data = &dma_mask_orion},
> +	{ .compatible = "marvell,ac5-ehci", .data = &dma_mask_ac5},
>  };
>  MODULE_DEVICE_TABLE(of, ehci_orion_dt_ids);
>  
> -- 
> 2.25.1
> 
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- This looks like a new version of a previously submitted patch, but you
  did not list below the --- line any changes from the previous version.
  Please read the section entitled "The canonical patch format" in the
  kernel file, Documentation/process/submitting-patches.rst for what
  needs to be done here to properly describe this.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot