From: Arnd Bergmann <arnd@arndb.de>
To: Nava kishore Manne <nava.manne@xilinx.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
michal.simek@xilinx.com, soren.brinkmann@xilinx.com,
balbi@ti.com, gregkh@linuxfoundation.org, hyun.kwon@xilinx.com,
navam@xilinx.com, radhey.shyam.pandey@xilinx.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Axi-usb: Add support for 64-bit addressing.
Date: Tue, 24 May 2016 10:50:37 +0200 [thread overview]
Message-ID: <14123451.MsNvJvqaJX@wuerfel> (raw)
In-Reply-To: <1464067268-35299-1-git-send-email-navam@xilinx.com>
On Tuesday, May 24, 2016 10:51:08 AM CEST Nava kishore Manne wrote:
> diff --git a/Documentation/devicetree/bindings/usb/udc-xilinx.txt b/Documentation/devicetree/bindings/usb/udc-xilinx.txt
> index 47b4e39..09df757 100644
> --- a/Documentation/devicetree/bindings/usb/udc-xilinx.txt
> +++ b/Documentation/devicetree/bindings/usb/udc-xilinx.txt
> @@ -1,18 +1,23 @@
> Xilinx USB2 device controller
>
> Required properties:
> -- compatible : Should be "xlnx,usb2-device-4.00.a"
> +- compatible : Should be "xlnx,usb2-device-4.00.a" or
> + "xlnx,usb2-device-5.00"
> - reg : Physical base address and size of the USB2
> device registers map.
> - interrupts : Should contain single irq line of USB2 device
> controller
> - xlnx,has-builtin-dma : if DMA is included
> +- dma-ranges : Should be as the following
> + <child-bus-address, parent-bus-address, length>
A USB host should not have any children that are DMA capable, I think, so this
property doesn't make sense here. It should be part of the parent bus.
> +- xlnx,addrwidth : Should be the dma addressing size in bits(ex: 64 bits)
I'm still unconvinced about the property definition here. What are the possible
options for the IP block? I don't think I ever saw a reply from you to my earlier
questions.
> @@ -214,6 +223,20 @@ static const struct usb_endpoint_descriptor config_bulk_out_desc = {
> .wMaxPacketSize = cpu_to_le16(EP0_MAX_PACKET),
> };
>
> +/**
> + * xudc_write64 - write 64bit value to device registers
> + * @addr: base addr of device registers
> + * @offset: register offset
> + * @val: data to be written
> + **/
> +static void xudc_write64(struct xusb_ep *ep, u32 offset, u64 val)
> +{
> + struct xusb_udc *udc = ep->udc;
> +
> + udc->write_fn(udc->addr, offset, lower_32_bits(val));
> + udc->write_fn(udc->addr, offset+0x04, upper_32_bits(val));
> +}
> +
> /**
> * xudc_write32 - little endian write to device registers
> * @addr: base addr of device registers
> @@ -330,8 +353,13 @@ static int xudc_start_dma(struct xusb_ep *ep, dma_addr_t src,
> * destination registers and then set the length
> * into the DMA length register.
> */
> - udc->write_fn(udc->addr, XUSB_DMA_DSAR_ADDR_OFFSET, src);
> - udc->write_fn(udc->addr, XUSB_DMA_DDAR_ADDR_OFFSET, dst);
> + if (udc->dma_addrwidth > 32) {
> + xudc_write64(ep, XUSB_DMA_DSAR_ADDR_OFFSET_LSB, src);
> + xudc_write64(ep, XUSB_DMA_DDAR_ADDR_OFFSET_LSB, dst);
> + } else {
> + udc->write_fn(udc->addr, XUSB_DMA_DSAR_ADDR_OFFSET, src);
> + udc->write_fn(udc->addr, XUSB_DMA_DDAR_ADDR_OFFSET, dst);
> + }
> udc->write_fn(udc->addr, XUSB_DMA_LENGTH_OFFSET, length);
>
This looks good.
Arnd
next prev parent reply other threads:[~2016-05-24 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 5:21 [PATCH v3] Axi-usb: Add support for 64-bit addressing Nava kishore Manne
2016-05-24 8:50 ` Arnd Bergmann [this message]
2016-05-24 11:47 ` Nava kishore Manne
2016-05-25 17:34 ` Rob Herring
2016-05-25 18:29 ` Arnd Bergmann
2016-05-25 18:53 ` Rob Herring
2016-05-30 5:46 ` Nava kishore Manne
2016-05-30 8:16 ` Arnd Bergmann
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=14123451.MsNvJvqaJX@wuerfel \
--to=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hyun.kwon@xilinx.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=nava.manne@xilinx.com \
--cc=navam@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=radhey.shyam.pandey@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=soren.brinkmann@xilinx.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