Received: by 10.192.165.148 with SMTP id m20csp3995991imm; Tue, 8 May 2018 00:45:47 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoGPEl/Ofy46NJZLBCt6fM/fY0zDJW6m3MrIWiqlBVOfBIoh/kUBNVcSGR5Vn/4QFenqzXE X-Received: by 2002:a63:2647:: with SMTP id m68-v6mr32075756pgm.56.1525765547328; Tue, 08 May 2018 00:45:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525765547; cv=none; d=google.com; s=arc-20160816; b=G2rdDqCVkJnEu4tB8gSlh1c45Fy+Jd24oq+eEWpmeSFLfiRcY2wHwSvdmHBbHNKnpb 2d+C9hQLzKKiPuxz3C+YfSSm1LMzc1pk4WOqOHFoyM2SzRPEptjYgi7ComXc/8G/bHNk 0MjMUDAcxWCR6OOGtgK3bSGROvFrgG0cmXctMkSjQfQ2muoTgd1TnknWHvKWwB+tdJyF XMtkktxqGeSaeHHbG9xzGTBsv8rS+7FYtR66OIkjlBZgx7Y8Fk/JUR7/iQbANO3G3Pbh CPcRiZL53ylMoFiIFb7ppRPI22D/4oENGkyXQSgSWlr2LfFzax5eUyNWkHQuuwTHz8k2 HocQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=xje1FNZAQ1nUhKgRxk+s0odwlAsjtTCAm8NloXwrJNI=; b=h5tsS1Hchl/WekHP+Ny8uaFQcgcf+k3/mfFNHxK9aRKvTPSBbo7OGZcdn+cBOAN4BX 8oUvkVRfCnhwU/5ZF3IKTzbfZPI+g0AnMB3Ayin4hE6fNvnugLAC9w+3cLugx9+FtCgz Ryu58dnFLGWtdTkBmgpfvjbDV8Zf44Tl5XZOvNoP9cOal0si037OJDQ4whaJ8fGBmX9K 7PxmEQKEn8YpuTtu25jsVtir8uTaLV9791AFUlJMYZgDR9DfhWCfGKgx/5xSZA7TqvW/ IdEwNWj6nfLsHhW4bBLv9KSjvFFjIIAGfaQjxJ0zCdVXNHMjeTntKfCvedYnPSsqqgrL lcgA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v7-v6si19625731pgq.608.2018.05.08.00.45.32; Tue, 08 May 2018 00:45:47 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754795AbeEHHoJ (ORCPT + 99 others); Tue, 8 May 2018 03:44:09 -0400 Received: from regular1.263xmail.com ([211.150.99.131]:44364 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754599AbeEHHoI (ORCPT ); Tue, 8 May 2018 03:44:08 -0400 Received: from wulf?rock-chips.com (unknown [192.168.167.160]) by regular1.263xmail.com (Postfix) with ESMTP id 5F8A9625E; Tue, 8 May 2018 15:44:01 +0800 (CST) X-263anti-spam: KSV:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 4 Received: from [172.16.12.54] (localhost [127.0.0.1]) by smtp.263.net (Postfix) with ESMTPA id 3D2BC387; Tue, 8 May 2018 15:43:55 +0800 (CST) X-IP-DOMAINF: 1 X-RL-SENDER: wulf@rock-chips.com X-FST-TO: milesschofield@aopen.com X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: wulf@rock-chips.com X-UNIQUE-TAG: <71a5b4fe9ad932ea2224971746d5a494> X-ATTACHMENT-NUM: 0 X-SENDER: wulf@rock-chips.com X-DNS-TYPE: 0 Received: from [172.16.12.54] (unknown [58.22.7.114]) by smtp.263.net (Postfix) whith ESMTP id 13641IQ1TUD; Tue, 08 May 2018 15:43:59 +0800 (CST) Subject: Re: [PATCH v3 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in To: Doug Anderson , William Wu Cc: hminas@synopsys.com, felipe.balbi@linux.intel.com, Greg Kroah-Hartman , Sergei Shtylyov , =?UTF-8?Q?Heiko_St=c3=bcbner?= , LKML , linux-usb@vger.kernel.org, "open list:ARM/Rockchip SoC..." , Frank Wang , =?UTF-8?B?6buE5rab?= , "daniel.meng" , John Youn , =?UTF-8?B?546L5b6B5aKe?= , zsq@rock-chips.com, =?UTF-8?B?6Kix5ZiJ6YqY?= , Stan Tsui , =?UTF-8?B?U3BydWNlIFd1ICjlkLPlu7rli7Mp?= , Martin.Tsai@quantatw.com, Kevin.Shai@quantatw.com, =?UTF-8?B?TW9uLUplciBXdSAo5ZCz5a2f5ZOyKQ==?= , =?UTF-8?B?Q2xhdWQgQ2hhbmcgKOW8teaBreeviSk=?= , =?UTF-8?B?U2FuIExpbiAo5p6X5bu66I+xKQ==?= , Ren.Kuo@quantatw.com, "David H.T. Wang" , Fong Lin , Steven Cheng , Tom Chen , donchang@aopen.com, milesschofield@aopen.com References: <1525748846-7767-1-git-send-email-william.wu@rock-chips.com> <1525748846-7767-2-git-send-email-william.wu@rock-chips.com> From: wlf Message-ID: Date: Tue, 8 May 2018 15:43:55 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Doug, 在 2018年05月08日 13:11, Doug Anderson 写道: > Hi, > > On Mon, May 7, 2018 at 8:07 PM, William Wu wrote: >> +static int dwc2_alloc_split_dma_aligned_buf(struct dwc2_hsotg *hsotg, >> + struct dwc2_qh *qh, >> + struct dwc2_host_chan *chan) >> +{ >> + if (!hsotg->unaligned_cache) >> + return -ENOMEM; >> + >> + if (!qh->dw_align_buf) { >> + qh->dw_align_buf = kmem_cache_alloc(hsotg->unaligned_cache, >> + GFP_ATOMIC | GFP_DMA); >> + if (!qh->dw_align_buf) >> + return -ENOMEM; >> + >> + qh->dw_align_buf_size = min_t(u32, chan->max_packet, >> + DWC2_KMEM_UNALIGNED_BUF_SIZE); > Rather than using min_t, wouldn't it be better to return -ENOMEM if > "max_packet" > DWC2_KMEM_UNALIGNED_BUF_SIZE? As it is, you might > allocate less space than you need, right? That seems like it would be > bad (even though this is probably impossible). Yes, good idea! So is it good to fix it like this? if (!qh->dw_align_buf || chan->max_packet > DWC2_KMEM_UNALIGNED_BUF_SIZE) return -ENOMEM; qh->dw_align_buf_size = chan->max_packet; > >> @@ -2797,6 +2837,32 @@ static int dwc2_assign_and_init_hc(struct dwc2_hsotg *hsotg, struct dwc2_qh *qh) >> /* Set the transfer attributes */ >> dwc2_hc_init_xfer(hsotg, chan, qtd); >> >> + /* For non-dword aligned buffers */ >> + if (hsotg->params.host_dma && qh->do_split && >> + chan->ep_is_in && (chan->xfer_dma & 0x3)) { >> + dev_vdbg(hsotg->dev, "Non-aligned buffer\n"); >> + if (dwc2_alloc_split_dma_aligned_buf(hsotg, qh, chan)) { >> + dev_err(hsotg->dev, >> + "Failed to allocate memory to handle non-aligned buffer\n"); >> + /* Add channel back to free list */ >> + chan->align_buf = 0; >> + chan->multi_count = 0; >> + list_add_tail(&chan->hc_list_entry, >> + &hsotg->free_hc_list); >> + qtd->in_process = 0; >> + qh->channel = NULL; >> + return -ENOMEM; >> + } >> + } else { >> + /* >> + * We assume that DMA is always aligned in non-split >> + * case or split out case. Warn if not. >> + */ >> + WARN_ON_ONCE(hsotg->params.host_dma && >> + (chan->xfer_dma & 0x3)); >> + chan->align_buf = 0; >> + } >> + >> if (chan->ep_type == USB_ENDPOINT_XFER_INT || >> chan->ep_type == USB_ENDPOINT_XFER_ISOC) >> /* >> @@ -5241,6 +5307,17 @@ int dwc2_hcd_init(struct dwc2_hsotg *hsotg) >> hsotg->params.dma_desc_enable = false; >> hsotg->params.dma_desc_fs_enable = false; >> } >> + } else if (hsotg->params.host_dma) { > Are you sure this is "else if"? Can't you have descriptor DMA enabled > in the controller and still need to do a normal DMA transfer if you > plug in a hub? Seems like this should be just "if". Sorry, I don't understand the case "have descriptor DMA enabled in the controller and still need to do a normal DMA transfer". But maybe it still has another problem if just use "if" here, because it will create kmem caches for Slave mode which actually doesn't need aligned DMA buf. > > >> + /* >> + * Create kmem caches to handle non-aligned buffer >> + * in Buffer DMA mode. >> + */ >> + hsotg->unaligned_cache = kmem_cache_create("dwc2-unaligned-dma", >> + DWC2_KMEM_UNALIGNED_BUF_SIZE, 4, > Worth using "DWC2_USB_DMA_ALIGN" rather than 4? > > >> + SLAB_CACHE_DMA, NULL); >> + if (!hsotg->unaligned_cache) >> + dev_err(hsotg->dev, >> + "unable to create dwc2 unaligned cache\n"); >> } >> >> hsotg->otg_port = 1; >> @@ -5279,6 +5356,7 @@ int dwc2_hcd_init(struct dwc2_hsotg *hsotg) >> error4: >> kmem_cache_destroy(hsotg->desc_gen_cache); >> kmem_cache_destroy(hsotg->desc_hsisoc_cache); >> + kmem_cache_destroy(hsotg->unaligned_cache); > nitty nit: freeing order should be opposite of allocation, so the new > line should be above the other two. Ah, I got it. But note that it's impossible to allocate the "unaligned_cache" and "desc *cache" at the same time. Should we still fix the free order? If yes, maybe the correct free order is: kmem_cache_destroy(hsotg->unaligned_cache); kmem_cache_destroy(hsotg->desc_hsisoc_cache); kmem_cache_destroy(hsotg->desc_gen_cache); Right? And should we also need to fix the same free order in the "dwc2_hcd_remove"? Best regards,         wulf > >