[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZ=vyPSiPCUppfDWC9OShqfe-BRvB5QjU1AZmbDbYvsZQ@mail.gmail.com>
Date: Mon, 30 Nov 2015 13:49:23 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Yendapally Reddy Dhananjaya Reddy <yrdreddy@...adcom.com>,
Stephen Warren <swarren@...dotorg.org>,
Ray Jui <rjui@...adcom.com>
Cc: Scott Branden <sbranden@...adcom.com>,
Jon Mason <jonmason@...adcom.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 2/3] pinctrl: nsp: add pinmux driver support for Broadcom
NSP SoC
On Fri, Nov 20, 2015 at 6:57 PM, Yendapally Reddy Dhananjaya Reddy
<yrdreddy@...adcom.com> wrote:
> This adds the initial support of the Broadcom NSP pinmux driver.
>
> Signed-off-by: Yendapally Reddy Dhananjaya Reddy <yrdreddy@...adcom.com>
So what does Ray and Stephen say about this?
Is the hardware unique enough to warrant its own driver?
Or should it utilize/extend one of the existing Broadcom
drivers?
Yours,
Linus Walleij
--
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