linux-mips
[Top] [All Lists]

Re: [PATCH 1/8] MIPS: Alchemy: abstract USB block control register acces

To: Manuel Lauss <manuel.lauss@googlemail.com>
Subject: Re: [PATCH 1/8] MIPS: Alchemy: abstract USB block control register access
From: Greg KH <gregkh@suse.de>
Date: Fri, 12 Aug 2011 09:04:54 -0700
Cc: Linux-MIPS <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>, linux-usb@vger.kernel.org
In-reply-to: <1313141985-5830-2-git-send-email-manuel.lauss@googlemail.com>
References: <1313141985-5830-1-git-send-email-manuel.lauss@googlemail.com> <1313141985-5830-2-git-send-email-manuel.lauss@googlemail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.21 (2010-09-15)
On Fri, Aug 12, 2011 at 11:39:38AM +0200, Manuel Lauss wrote:
> Alchemy chips have one or more registers which control access
> to the usb blocks as well as PHY configuration.  I don't want
> the OHCI/EHCI glues to know about the different registers and bits;
> new arch code hides the gory details of USB configuration from them.
> 
> Cc: linux-usb@vger.kernel.org
> Cc: Greg Kroah-Hartman <gregkh@suse.de>  (USB glue parts)
> Signed-off-by: Manuel Lauss <manuel.lauss@googlemail.com>
> ---
> CC'ed Greg for an Ack on the USB glue parts.  I'd like this to go through the
>  MIPS tree since other changes in it depend on it.

Fine with me on the USB portions, you are just deleting code, which I
like :)

But should the "common" USB code really live under arch/mips/alchemy/ ?
The goal is to move driver code out of arch/ and into drivers/.  Why are
you moving stuff backwards here?

greg k-h

<Prev in Thread] Current Thread [Next in Thread>