linux-kernel - RE: [PATCH] usb: gadget: fsl: Set dma

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <9df06ff88cb44b48bf2fce71bdf78e03@BN1PR03MB251.namprd03.prod.outlook.com>
Date:	Fri, 14 Mar 2014 20:53:13 +0000
From:	"suresh.gupta@...escale.com" <suresh.gupta@...escale.com>
To:	"balbi@...com" <balbi@...com>
CC:	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] usb: gadget: fsl: Set dma_ops for FSL USB Gadget Device

Hi,

-----Original Message-----
From: Felipe Balbi [mailto:balbi@...com] 
Sent: Thursday, March 13, 2014 8:57 PM
To: Gupta Suresh-B42813
Cc: balbi@...com; gregkh@...uxfoundation.org; linux-usb@...r.kernel.org; linux-kernel@...r.kernel.org; Gupta Suresh-B42813
Subject: Re: [PATCH] usb: gadget: fsl: Set dma_ops for FSL USB Gadget Device

Hi,

On Thu, Mar 13, 2014 at 07:37:12PM +0530, Suresh Gupta wrote:
> From: Suresh Gupta <B42813@...escale.com>

return -ENOLOG

> Signed-off-by: Suresh Gupta <B42813@...escale.com>
> ---
>  drivers/usb/gadget/fsl_udc_core.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/usb/gadget/fsl_udc_core.c 
> b/drivers/usb/gadget/fsl_udc_core.c
> index 35b20e6..2a43d9d 100644
> --- a/drivers/usb/gadget/fsl_udc_core.c
> +++ b/drivers/usb/gadget/fsl_udc_core.c
> @@ -2456,6 +2456,7 @@ static int __init fsl_udc_probe(struct platform_device *pdev)
>  	/* Setup gadget.dev and register with kernel */
>  	dev_set_name(&udc_controller->gadget.dev, "gadget");
>  	udc_controller->gadget.dev.of_node = pdev->dev.of_node;
> +	set_dma_ops(&udc_controller->gadget.dev, 
> +pdev->dev.archdata.dma_ops);

why is the driver doing this ? Why is the driver given knowledge about details on archdata ?

Why do you need this at all ?
[SuresH] This is due to moving mapping virtual address functions 
to common "udc-core.c" where for example the dma_map_single expect dma_ops of gadget device. 
Before we call this function from our file with argument dma_map_single(ep->udc->gadget.dev.parent,.....

----
Thanks
SuresH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/