public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "hch@lst.de" <hch@lst.de>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"marex@denx.de" <marex@denx.de>, Leo Li <leoyang.li@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"noring@nocrew.org" <noring@nocrew.org>,
	"JuergenUrban@gmx.de" <JuergenUrban@gmx.de>
Subject: Re: [PATCH v5 2/5] USB: use genalloc for USB HCs with local memory
Date: Wed, 22 May 2019 10:45:35 +0000	[thread overview]
Message-ID: <cb0612c3-4429-7ac9-e885-64407f8a406b@nxp.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1905211309270.1634-100000@iolanthe.rowland.org>

Hello Alan,

On 21.05.2019 20:20, Alan Stern wrote:
> On Tue, 21 May 2019 laurentiu.tudor@nxp.com wrote:
> 
>> From: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>>
>> For HCs that have local memory, replace the current DMA API usage
>> with a genalloc generic allocator to manage the mappings for these
>> devices. To help users, introduce a new HCD API,
>> usb_hcd_setup_local_mem() that will setup up the genalloc backing
>> up the device local memory. It will be used in subsequent patches.
>> This is in preparation for dropping the existing "coherent" dma
>> mem declaration APIs. Current implementation was relying on a short
>> circuit in the DMA API that in the end, was acting as an allocator
>> for these type of devices.
>>
>> For context, see thread here: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flkml.org%2Flkml%2F2019%2F4%2F22%2F357&amp;data=02%7C01%7Claurentiu.tudor%40nxp.com%7Cdc4a76b04b874b75bd5408d6de109d86%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636940560281957207&amp;sdata=JQ1iJc%2Fw%2BwHdTFvaOT%2FYHBx%2BVQlpHWlf346q7sclfcg%3D&amp;reserved=0
>>
>> Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com>
>> Signed-off-by: Fredrik Noring <noring@nocrew.org>
>> ---
> 
>> --- a/drivers/usb/core/hcd.c
>> +++ b/drivers/usb/core/hcd.c
>> @@ -29,6 +29,8 @@
>>   #include <linux/workqueue.h>
>>   #include <linux/pm_runtime.h>
>>   #include <linux/types.h>
>> +#include <linux/genalloc.h>
>> +#include <linux/io.h>
>>   
>>   #include <linux/phy/phy.h>
>>   #include <linux/usb.h>
>> @@ -3039,6 +3041,40 @@ usb_hcd_platform_shutdown(struct platform_device *dev)
>>   }
>>   EXPORT_SYMBOL_GPL(usb_hcd_platform_shutdown);
>>   
>> +int usb_hcd_setup_local_mem(struct usb_hcd *hcd, phys_addr_t phys_addr,
>> +			    dma_addr_t dma, size_t size)
>> +{
>> +	int err;
>> +	void __iomem *local_mem;
>> +
>> +	hcd->localmem_pool = devm_gen_pool_create(hcd->self.sysdev, PAGE_SHIFT,
>> +						  dev_to_node(hcd->self.sysdev),
>> +						  "ohci-hcd");
> 
> Surely that string is a mistake.  You could use
> dev_name(hcd->self.sysdev) or a name passed by the caller.

Sorry, missed that. Will go with dev_name() if that's ok with you.

>> +	if (IS_ERR(hcd->localmem_pool))
>> +		return PTR_ERR(hcd->localmem_pool);
>> +
>> +	local_mem = devm_memremap(hcd->self.sysdev, phys_addr,
>> +				  size, MEMREMAP_WC);
>> +	if (!local_mem)
>> +		return -ENOMEM;
>> +
>> +	/*
>> +	 * Here we pass a dma_addr_t but the arg type is a phys_addr_t.
>> +	 * It's not backed by system memory and thus there's no kernel mapping
>> +	 * for it.
>> +	 */
>> +	err = gen_pool_add_virt(hcd->localmem_pool, (unsigned long)local_mem,
>> +				dma, size, dev_to_node(hcd->self.sysdev));
>> +	if (err < 0) {
>> +		dev_err(hcd->self.sysdev, "gen_pool_add_virt failed with %d\n",
>> +			err);
>> +		return err;
>> +	}
>> +
>> +	return 0;
>> +}
>> +EXPORT_SYMBOL_GPL(usb_hcd_setup_local_mem);
> 
> If you have a usb_hcd_setup_local_mem() function then you should also
> have a usb_hcd_remove_local_mem() function.

Even if all resources that are allocated are device managed?

>> --- a/drivers/usb/host/ohci-mem.c
>> +++ b/drivers/usb/host/ohci-mem.c
>> @@ -36,6 +36,12 @@ static void ohci_hcd_init (struct ohci_hcd *ohci)
>>   
>>   static int ohci_mem_init (struct ohci_hcd *ohci)
>>   {
>> +	if (ohci_to_hcd(ohci)->localmem_pool) {
>> +		ohci->td_cache = NULL;
>> +		ohci->ed_cache = NULL;
>> +		return 0;
>> +	}
> 
> This really isn't necessary.  The entire ohci_hcd structure is
> initialized to 0 when it is first allocated.

Will drop.

>> --- a/include/linux/usb/hcd.h
>> +++ b/include/linux/usb/hcd.h
>> @@ -216,6 +216,9 @@ struct usb_hcd {
>>   #define	HC_IS_RUNNING(state) ((state) & __ACTIVE)
>>   #define	HC_IS_SUSPENDED(state) ((state) & __SUSPEND)
>>   
>> +	/* allocator for HCs having local memory */
> 
> "allocator" is the wrong word -- an allocator is something that
> allocates.  Perhaps "memory area" or something along those lines.

Alright, I will rework.

---
Thanks & Best Regards, Laurentiu

  reply	other threads:[~2019-05-22 10:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 14:07 [PATCH v5 0/5] prerequisites for device reserved local mem rework laurentiu.tudor
2019-05-21 14:07 ` [PATCH v5 1/5] lib/genalloc.c: Add gen_pool_dma_zalloc() for zeroed DMA allocations laurentiu.tudor
2019-05-21 14:07 ` [PATCH v5 2/5] USB: use genalloc for USB HCs with local memory laurentiu.tudor
2019-05-21 15:27   ` Fredrik Noring
2019-05-22 10:54     ` Laurentiu Tudor
2019-05-21 17:20   ` Alan Stern
2019-05-22 10:45     ` Laurentiu Tudor [this message]
2019-05-22 14:58       ` Alan Stern
2019-05-21 14:07 ` [PATCH v5 3/5] usb: host: ohci-sm501: init genalloc for " laurentiu.tudor
2019-05-21 14:07 ` [PATCH v5 4/5] usb: host: ohci-tmio: " laurentiu.tudor
2019-05-21 14:07 ` [PATCH v5 5/5] USB: drop HCD_LOCAL_MEM flag laurentiu.tudor

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=cb0612c3-4429-7ac9-e885-64407f8a406b@nxp.com \
    --to=laurentiu.tudor@nxp.com \
    --cc=JuergenUrban@gmx.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=leoyang.li@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=noring@nocrew.org \
    --cc=robin.murphy@arm.com \
    --cc=stern@rowland.harvard.edu \
    /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