linux-kernel - RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <C89496FEAE474D468F30D558A9468D9F26CF8BC0@XAP-PVEXMBX01.xlnx.xilinx.com>
Date:	Mon, 11 Jul 2016 10:07:31 +0000
From:	Nava kishore Manne <nava.manne@...inx.com>
To:	Rob Herring <robh@...nel.org>
CC:	"pawel.moll@....com" <pawel.moll@....com>,
	"mark.rutland@....com" <mark.rutland@....com>,
	"ijc+devicetree@...lion.org.uk" <ijc+devicetree@...lion.org.uk>,
	"galak@...eaurora.org" <galak@...eaurora.org>,
	Michal Simek <michals@...inx.com>,
	Soren Brinkmann <sorenb@...inx.com>,
	"balbi@...com" <balbi@...com>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	Hyun Kwon <hyunk@...inx.com>,
	Radhey Shyam Pandey <radheys@...inx.com>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.

Ping!!

> -----Original Message-----
> From: Nava kishore Manne
> Sent: Monday, June 27, 2016 6:18 PM
> To: 'Rob Herring' <robh@...nel.org>
> Cc: pawel.moll@....com; mark.rutland@....com;
> ijc+devicetree@...lion.org.uk; galak@...eaurora.org; Michal Simek
> <michals@...inx.com>; Soren Brinkmann <sorenb@...inx.com>;
> balbi@...com; gregkh@...uxfoundation.org; Hyun Kwon
> <hyunk@...inx.com>; Radhey Shyam Pandey <radheys@...inx.com>;
> devicetree@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; linux-
> kernel@...r.kernel.org
> Subject: RE: [PATCH v4] Axi-usb: Add support for 64-bit addressing.
>
> Ping!!
>
> > -----Original Message-----
> > From: Rob Herring [mailto:robh@...nel.org]
> > Sent: Friday, June 03, 2016 4:28 AM
> > To: Nava kishore Manne <navam@...inx.com>
> > Cc: pawel.moll@....com; mark.rutland@....com;
> > ijc+devicetree@...lion.org.uk; galak@...eaurora.org; Michal Simek
> > <michals@...inx.com>; Soren Brinkmann <sorenb@...inx.com>;
> > balbi@...com; gregkh@...uxfoundation.org; Hyun Kwon
> > <hyunk@...inx.com>; Nava kishore Manne <navam@...inx.com>; Radhey
> > Shyam Pandey <radheys@...inx.com>; devicetree@...r.kernel.org; linux-
> > arm-kernel@...ts.infradead.org; linux-kernel@...r.kernel.org
> > Subject: Re: [PATCH v4] Axi-usb: Add support for 64-bit addressing.
> >
> > On Mon, May 30, 2016 at 10:16:38PM +0530, Nava kishore Manne wrote:
> > > This patch updates the driver to support 64-bit DMA addressing.
> > >
> > > Signed-off-by: Nava kishore Manne <navam@...inx.com>
> > > ---
> > > Changes for v4:
> > >           -Used boolen property insted of addrwith property in the DT
> > >            as suggested by Arnd Bergmann.
> > >           -Adopt the DT relevant changes into the driver.
> > >
> > > Changes for v3:
> > >                 -Added new compatable string for 5.00 IP version as suggested by
> > >                  Arnd Bergmann.
> > >                 -Used write_fn() insted of lo_hi_writeq() as suggested by
> > >                  Arnd Bergmann.
> > >
> > > Changes for v2:
> > >                 -Added dma-ranges property in device tree as
> > > suggested by Arnd
> > Bergmann.
> > >                 -Modified the driver code based on the xlnx,addrwidth.
> > >
> > >  .../devicetree/bindings/usb/udc-xilinx.txt         |  5 ++-
> >
> > Acked-by: Rob Herring <robh@...nel.org>
> >
> > >  drivers/usb/gadget/udc/udc-xilinx.c                | 52
> > +++++++++++++++++++++-
> > >  2 files changed, 54 insertions(+), 3 deletions(-)


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.