[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140821140040.GE9608@saruman.home>
Date: Thu, 21 Aug 2014 09:00:40 -0500
From: Felipe Balbi <balbi@...com>
To: sundeep subbaraya <sundeep.lkml@...il.com>
CC: Daniel Mack <daniel@...que.org>,
Subbaraya Sundeep Bhatta <subbaraya.sundeep.bhatta@...inx.com>,
"balbi@...com" <balbi@...com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michal Simek <michals@...inx.com>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
<svemula@...inx.com>, <anirudh@...inx.com>,
Subbaraya Sundeep Bhatta <sbhatta@...inx.com>
Subject: Re: [PATCH v4 2/2] usb: gadget: Add xilinx usb2 device support
On Thu, Aug 21, 2014 at 12:19:03PM +0530, sundeep subbaraya wrote:
> Hi Daniel,
>
> On Tue, Aug 19, 2014 at 3:26 PM, Daniel Mack <daniel@...que.org> wrote:
> > Hi,
> >
> > On 07/22/2014 11:08 AM, Subbaraya Sundeep Bhatta wrote:
> >> This patch adds xilinx usb2 device driver support
> >
> > Add some more information here, please. Copying the text from the
> > Kconfig option is already a good start.
> >
> >> drivers/usb/gadget/Kconfig | 14 +
> >> drivers/usb/gadget/Makefile | 1 +
> >> drivers/usb/gadget/udc-xilinx.c | 2261 +++++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 2276 insertions(+), 0 deletions(-)
> >> create mode 100644 drivers/usb/gadget/udc-xilinx.c
> >
> > As your driver has a DT binding, you have to describe it in
> > Documentation/devicetree/bindings.
> >
> >> --- a/drivers/usb/gadget/Kconfig
> >> +++ b/drivers/usb/gadget/Kconfig
> >> @@ -459,6 +459,20 @@ config USB_EG20T
> >> ML7213/ML7831 is companion chip for Intel Atom E6xx series.
> >> ML7213/ML7831 is completely compatible for Intel EG20T PCH.
> >>
> >> +config USB_GADGET_XILINX
> >> + tristate "Xilinx USB Driver"
> >> + depends on COMPILE_TEST
> >
> > Why would you depend on that?
>
> Felipe asked to make this since this is USB soft IP driver and its
> dependencies have tendency to grow.
that's not exactly what I asked :-) Usually you only add COMPILE_TEST
when you have an ARCH dependency. So something like:
depends on ARCH_ARM || COMPILE_TEST
would make it clear that this driver is only available on ARM, but when
doing my build tests, I'd still be able to compile it on x86.
> > Also, your code uses device tree functions unconditionally, which is
> > fine, but it must hence depend on 'OF'.
>
> Ok will add OF along with COMPILE_TEST
so this would be:
depends on OF || COMPILE_TEST
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists