Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755448AbaDTQ7R (ORCPT ); Sun, 20 Apr 2014 12:59:17 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:55024 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751046AbaDTQ7O (ORCPT ); Sun, 20 Apr 2014 12:59:14 -0400 Date: Sun, 20 Apr 2014 09:58:37 -0700 From: Greg KH To: Punnaiah Choudary Kalluri Cc: leoli@freescale.com, balbi@ti.com, michal.simek@xilinx.com, linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, linux-usb@vger.kernel.org, kalluripunnaiahchoudary@gmail.com, kpc528@gmail.com, Punnaiah Choudary Kalluri Subject: Re: [RFC PATCH 0/2] usb: Reuse fsl driver code for synopsys usb controller Message-ID: <20140420165837.GA5423@kroah.com> References: <7aed4ee6-69e7-4f9f-9f45-675bc695089c@CO9EHSMHS031.ehs.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7aed4ee6-69e7-4f9f-9f45-675bc695089c@CO9EHSMHS031.ehs.local> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 20, 2014 at 09:57:03PM +0530, Punnaiah Choudary Kalluri wrote: > Zynq soc contains a dual role usb controller and this IP is from synopsys. We > observed that there is driver available for this controller from freescale and > decided to reuse this driver for zynq use. > > Here is the link for zynq soc TRM. Please refer chapter 15 for usb controller > related information. > http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf > > The following series of patches add initial support for zynq soc in fsl gadget controller > driver and fsl host controller driver. > > Based on these patches, I have the following concerns and sugesstions > > Since the freescale usb driver is for synopsys IP, Please consider rebranding > this driver name and config options to reflect that it is a sysnopsys IP. So > that other vendors who using this IP can reuse thie driver. The config options can be edited to show the new hardware support, but we don't usually rename kernel drivers, sorry. That just gets messy in the end, and the "first one here gets to name it" is usually enforced. No users ever see a kernel driver name, especially for a gadget driver, so it shouldn't ever really matter. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/