Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753933AbbK3Mt0 (ORCPT ); Mon, 30 Nov 2015 07:49:26 -0500 Received: from mail-ob0-f180.google.com ([209.85.214.180]:35232 "EHLO mail-ob0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752352AbbK3MtY (ORCPT ); Mon, 30 Nov 2015 07:49:24 -0500 MIME-Version: 1.0 In-Reply-To: <1448042245-25702-1-git-send-email-yrdreddy@broadcom.com> References: <1448042245-25702-1-git-send-email-yrdreddy@broadcom.com> Date: Mon, 30 Nov 2015 13:49:23 +0100 Message-ID: Subject: Re: [PATCH 2/3] pinctrl: nsp: add pinmux driver support for Broadcom NSP SoC From: Linus Walleij To: Yendapally Reddy Dhananjaya Reddy , Stephen Warren , Ray Jui Cc: Scott Branden , Jon Mason , "linux-kernel@vger.kernel.org" , "linux-gpio@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , bcm-kernel-feedback-list Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 681 Lines: 21 On Fri, Nov 20, 2015 at 6:57 PM, Yendapally Reddy Dhananjaya Reddy wrote: > This adds the initial support of the Broadcom NSP pinmux driver. > > Signed-off-by: Yendapally Reddy Dhananjaya Reddy 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/