[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77a9809bf6a8476c80d9308a7d3b1ac0@BN1AFFO11FD047.protection.gbl>
Date: Wed, 5 Nov 2014 09:14:00 -0800
From: Sören Brinkmann <soren.brinkmann@...inx.com>
To: Andreas Färber <afaerber@...e.de>
CC: Linus Walleij <linus.walleij@...aro.org>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Heiko Stuebner <heiko@...ech.de>, <linux-sh@...r.kernel.org>,
Michal Simek <michal.simek@...inx.com>,
<linux-kernel@...r.kernel.org>,
<linux-rockchip@...ts.infradead.org>,
<linux-arm-kernel@...ts.infradead.org>,
Alessandro Rubini <rubini@...pv.it>
Subject: Re: [PATCH 5/7] pinctrl: Add driver for Zynq
On Wed, 2014-11-05 at 06:12AM +0100, Andreas Färber wrote:
> Am 03.11.2014 um 20:05 schrieb Soren Brinkmann:
> > +enum zynq_pinmux_functions {
> > + ZYNQ_PMUX_ethernet0,
> > + ZYNQ_PMUX_ethernet1,
> > + ZYNQ_PMUX_mdio0,
> > + ZYNQ_PMUX_mdio1,
> > + ZYNQ_PMUX_qspi0,
> > + ZYNQ_PMUX_qspi1,
> > + ZYNQ_PMUX_qspi_fbclk,
> > + ZYNQ_PMUX_qspi_cs1,
>
> Are usb0 and usb1 intentionally missing in this patch for lack of
> upstream USB driver? If so, then please mention what you left out in the
> commit message.
I don't know how that could happen, but no, it's not intentionally
missing, let's call it accidentally. It just slipped through. Don't
ask me how I could miss USB.
Thanks,
Sören
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists