devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Rob Herring <robh@kernel.org>
Cc: Nava kishore Manne <nava.manne@xilinx.com>,
	"pawel.moll@arm.com" <pawel.moll@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"ijc+devicetree@hellion.org.uk" <ijc+devicetree@hellion.org.uk>,
	"galak@codeaurora.org" <galak@codeaurora.org>,
	Michal Simek <michals@xilinx.com>,
	Soren Brinkmann <sorenb@xilinx.com>,
	"balbi@ti.com" <balbi@ti.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	Hyun Kwon <hyunk@xilinx.com>,
	Radhey Shyam Pandey <radheys@xilinx.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Axi-usb: Add support for 64-bit addressing.
Date: Wed, 25 May 2016 20:29:40 +0200	[thread overview]
Message-ID: <5392766.vCAWrASuOA@wuerfel> (raw)
In-Reply-To: <20160525173419.GA7510@rob-hp-laptop>

On Wednesday, May 25, 2016 12:34:19 PM CEST Rob Herring wrote:
> On Tue, May 24, 2016 at 11:47:31AM +0000, Nava kishore Manne wrote:
> > 
> > 
> > > -----Original Message-----
> > > From: Arnd Bergmann [mailto:arnd@arndb.de]
> > > Sent: Tuesday, May 24, 2016 2:21 PM
> > > To: Nava kishore Manne <navam@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
> > > <michals@xilinx.com>; Soren Brinkmann <sorenb@xilinx.com>;
> > > balbi@ti.com; gregkh@linuxfoundation.org; Hyun Kwon
> > > <hyunk@xilinx.com>; Nava kishore Manne <navam@xilinx.com>; Radhey
> > > Shyam Pandey <radheys@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.
> > > 
> > > 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.
> > > 
> > Will send next version (v4) by removing this property from the DT.
> > 
> > > > +- 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.
> > > 
> > 
> > Sorry Let me clearly explain
> > 
> > From the IP version 5.0 onwards The IP support both 32-bit and 64-bit addressing.
> > But the older version of the IP's supports only 32-bit addressing.
> > 
> > This addrwidth property differentiates the address width for the new IP (I mean 5.0 version on wards)
> > For older IP it will be always 32-bit.
> 
> Then I think you should have a simple boolean property for 64-bit 
> configuration.

I think matching on the version number is slightly better, as we have the version
already and it identifies whether the register exists.

Having a boolean property of course works as well, it just duplicates that
information.

	Arnd

  reply	other threads:[~2016-05-25 18:29 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
2016-05-24 11:47   ` Nava kishore Manne
2016-05-25 17:34     ` Rob Herring
2016-05-25 18:29       ` Arnd Bergmann [this message]
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=5392766.vCAWrASuOA@wuerfel \
    --to=arnd@arndb.de \
    --cc=balbi@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hyunk@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=michals@xilinx.com \
    --cc=nava.manne@xilinx.com \
    --cc=pawel.moll@arm.com \
    --cc=radheys@xilinx.com \
    --cc=robh@kernel.org \
    --cc=sorenb@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;
as well as URLs for NNTP newsgroup(s).