From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vaibhav Hiremath Subject: Re: [PATCH-v5 1/5] Documentation: binding: add new property 'disable_after_xfer' to i2c-pxa Date: Wed, 05 Aug 2015 12:04:25 +0530 Message-ID: <55C1AE71.3010700@linaro.org> References: <1437482466-16126-1-git-send-email-vaibhav.hiremath@linaro.org> <1437482466-16126-2-git-send-email-vaibhav.hiremath@linaro.org> <20150727140911.GB15004@beef> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150727140911.GB15004@beef> Sender: linux-kernel-owner@vger.kernel.org To: Matt Porter Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, wsa@the-dreams.de, linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org, robert.jarzmik@free.fr List-Id: linux-i2c@vger.kernel.org On Monday 27 July 2015 07:39 PM, Matt Porter wrote: > On Tue, Jul 21, 2015 at 06:11:02PM +0530, Vaibhav Hiremath wrote: >> Driver will now supports enable/disable across msg xfer, which user >> can control it by new DT property - >> >> i2c-disable-after-xfer : If set, driver will disable I2C module after msg >> xfer and enable it back before xfer. > > If this is a new property specific to this Marvell part, it needs > the vendor prefix as in mrvl,i2c-disable-after-xfer > We discussed about this, I think in V1 or V2. Decided to use generic name, as feature (in turn property) could be used by other drivers as well. > Or, it couldn't hurt to start an i2c.txt for generic i2c bindings > and store it there as this and others later in this series would > reasonably apply to other controllers. > Yeah, we could start i2c.txt, probably better to have separate new patch all together. Thanks, Vaibhav