From: Jayshri Pawar <jpawar@cadence.com>
To: <linux-usb@vger.kernel.org>
Cc: <gregkh@linuxfoundation.org>, <felipe.balbi@linux.intel.com>,
<heikki.krogerus@linux.intel.com>, <rogerq@ti.com>,
<linux-kernel@vger.kernel.org>, <jbergsagel@ti.com>,
<nsekhar@ti.com>, <nm@ti.com>, <peter.chen@nxp.com>,
<kurahul@cadence.com>, <pawell@cadence.com>,
<sparmar@cadence.com>, <jpawar@cadence.com>
Subject: [RFC PATCH] usb: gadget: f_tcm: Added DMA32 flag while allocation of command buffer
Date: Wed, 13 Nov 2019 10:24:32 +0000 [thread overview]
Message-ID: <1573640672-10344-1-git-send-email-jpawar@cadence.com> (raw)
There is a problem when function driver allocate memory for buffer
used by DMA from outside dma_mask space.
It appears during testing f_tcm driver with cdns3 controller.
In the result cdns3 driver was not able to map virtual buffer to DMA.
This fix should be improved depending on dma_mask associated with device.
Adding GFP_DMA32 flag while allocationg command data buffer only for 32
bit controllers.
Signed-off-by: Pawel Laszczak <pawell@cadence.com>
Signed-off-by: Jayshri Pawar <jpawar@cadence.com>
---
drivers/usb/gadget/function/f_tcm.c | 20 ++++++++++++++------
include/linux/usb/gadget.h | 2 ++
2 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/gadget/function/f_tcm.c b/drivers/usb/gadget/function/f_tcm.c
index 36504931b2d1..a78d5fad3d84 100644
--- a/drivers/usb/gadget/function/f_tcm.c
+++ b/drivers/usb/gadget/function/f_tcm.c
@@ -213,7 +213,8 @@ static int bot_send_read_response(struct usbg_cmd *cmd)
}
if (!gadget->sg_supported) {
- cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC);
+ cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC |
+ gadget->dma_flag);
if (!cmd->data_buf)
return -ENOMEM;
@@ -257,7 +258,8 @@ static int bot_send_write_request(struct usbg_cmd *cmd)
}
if (!gadget->sg_supported) {
- cmd->data_buf = kmalloc(se_cmd->data_length, GFP_KERNEL);
+ cmd->data_buf = kmalloc(se_cmd->data_length, GFP_KERNEL |
+ gadget->dma_flag);
if (!cmd->data_buf)
return -ENOMEM;
@@ -305,6 +307,7 @@ static void bot_cmd_complete(struct usb_ep *ep, struct usb_request *req)
static int bot_prepare_reqs(struct f_uas *fu)
{
int ret;
+ struct usb_gadget *gadget = fuas_to_gadget(fu);
fu->bot_req_in = usb_ep_alloc_request(fu->ep_in, GFP_KERNEL);
if (!fu->bot_req_in)
@@ -327,7 +330,8 @@ static int bot_prepare_reqs(struct f_uas *fu)
fu->bot_status.req->complete = bot_status_complete;
fu->bot_status.csw.Signature = cpu_to_le32(US_BULK_CS_SIGN);
- fu->cmd.buf = kmalloc(fu->ep_out->maxpacket, GFP_KERNEL);
+ fu->cmd.buf = kmalloc(fu->ep_out->maxpacket, GFP_KERNEL |
+ gadget->dma_flag);
if (!fu->cmd.buf)
goto err_buf;
@@ -515,7 +519,8 @@ static int uasp_prepare_r_request(struct usbg_cmd *cmd)
struct uas_stream *stream = cmd->stream;
if (!gadget->sg_supported) {
- cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC);
+ cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC |
+ gadget->dma_flag);
if (!cmd->data_buf)
return -ENOMEM;
@@ -763,11 +768,13 @@ static int uasp_alloc_stream_res(struct f_uas *fu, struct uas_stream *stream)
static int uasp_alloc_cmd(struct f_uas *fu)
{
+ struct usb_gadget *gadget = fuas_to_gadget(fu);
fu->cmd.req = usb_ep_alloc_request(fu->ep_cmd, GFP_KERNEL);
if (!fu->cmd.req)
goto err;
- fu->cmd.buf = kmalloc(fu->ep_cmd->maxpacket, GFP_KERNEL);
+ fu->cmd.buf = kmalloc(fu->ep_cmd->maxpacket, GFP_KERNEL |
+ gadget->dma_flag);
if (!fu->cmd.buf)
goto err_buf;
@@ -980,7 +987,8 @@ static int usbg_prepare_w_request(struct usbg_cmd *cmd, struct usb_request *req)
struct usb_gadget *gadget = fuas_to_gadget(fu);
if (!gadget->sg_supported) {
- cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC);
+ cmd->data_buf = kmalloc(se_cmd->data_length, GFP_ATOMIC |
+ gadget->dma_flag);
if (!cmd->data_buf)
return -ENOMEM;
diff --git a/include/linux/usb/gadget.h b/include/linux/usb/gadget.h
index 124462d65eac..d6c9cd222600 100644
--- a/include/linux/usb/gadget.h
+++ b/include/linux/usb/gadget.h
@@ -373,6 +373,7 @@ struct usb_gadget_ops {
* @connected: True if gadget is connected.
* @lpm_capable: If the gadget max_speed is FULL or HIGH, this flag
* indicates that it supports LPM as per the LPM ECN & errata.
+ * @dma_flag: dma zone to be used for buffer allocation.
*
* Gadgets have a mostly-portable "gadget driver" implementing device
* functions, handling all usb configurations and interfaces. Gadget
@@ -427,6 +428,7 @@ struct usb_gadget {
unsigned deactivated:1;
unsigned connected:1;
unsigned lpm_capable:1;
+ unsigned int dma_flag;
};
#define work_to_gadget(w) (container_of((w), struct usb_gadget, work))
--
2.20.1
next reply other threads:[~2019-11-13 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 10:24 Jayshri Pawar [this message]
2019-11-14 2:50 ` Peter Chen
2019-11-14 9:48 ` Roger Quadros
2019-11-15 10:14 ` Jayshri Dajiram Pawar
2019-11-15 11:11 ` Roger Quadros
2019-11-15 18:02 ` Konrad Rzeszutek Wilk
2019-11-22 11:55 ` Jayshri Dajiram Pawar
2019-11-25 16:31 ` Konrad Rzeszutek Wilk
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=1573640672-10344-1-git-send-email-jpawar@cadence.com \
--to=jpawar@cadence.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jbergsagel@ti.com \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.com \
--cc=sparmar@cadence.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®