Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755436Ab3HWPWW (ORCPT ); Fri, 23 Aug 2013 11:22:22 -0400 Received: from smtp2-1.goneo.de ([212.90.139.83]:46646 "EHLO smtp2-1.goneo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755256Ab3HWPWU (ORCPT ); Fri, 23 Aug 2013 11:22:20 -0400 X-Spam-Flag: NO X-Spam-Score: -2.856 From: Lars Poeschel To: Mark Rutland Subject: Re: [PATCH 1/2] gpio: mcp23s08: rename the device tree property Date: Fri, 23 Aug 2013 17:22:10 +0200 User-Agent: KMail/1.13.7 (Linux/3.10-2-amd64; KDE/4.8.4; x86_64; ; ) Cc: Lars Poeschel , "grant.likely@linaro.org" , "linus.walleij@linaro.org" , "rob.herring@calxeda.com" , Pawel Moll , "swarren@wwwdotorg.org" , "ian.campbell@citrix.com" , "rob@landley.net" , "arnd@arndb.de" , "linux-doc@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-gpio@vger.kernel.org" References: <1377165378-9589-1-git-send-email-larsi@wh2.tu-dresden.de> <20130823142421.GK25856@e106331-lin.cambridge.arm.com> In-Reply-To: <20130823142421.GK25856@e106331-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201308231722.10392.poeschel@lemonage.de> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1814 Lines: 44 On Friday 23 August 2013 at 16:24:21, Mark Rutland wrote: > On Thu, Aug 22, 2013 at 10:56:17AM +0100, Lars Poeschel wrote: > > From: Lars Poeschel > > > > The device tree property should be more descriptive. > > microchip seems more reasonable than mcp. As there are no > > in tree users of this property, so the rename can still be > > done without pain. > > Are there definitely no users? I see there are no dts with a > "mcp,mcp23***" compatible string, but are there any boards already out > there with this hardware that someone might be using and a currently > release kernel supports? What do you mean by "release"? The device tree support for the gpio- mcp23s08 driver and thus the "mcp" string came in with v3.9. This is stable but not longterm. > With the bcm/broadcom => brcm change, we marked the old vendor prefix as > deprecated (but left the support code). > > If we can 100% guarantee no-one's using the compatible string, I'm happy > to change it. Otherwise we just have to mark the old string as > deprecated. I am the developer of the device tree support for that driver and I am not aware of any user, but surely I can not guarantee it. I never imagined how hard it would be. ;-) I presented both variants: 1.) simply add mcp to vendor-prefixes.txt 2.) change the driver to microchip and add microchip to vendor-prefixes.txt May one of the maintainers decide which one to take or even take none of the patches. Or do you need a third variant with both strings in the driver and microchip in vendor-prefixes? Lars -- 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/