devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav Hiremath <vaibhav.hiremath@linaro.org>
To: Matt Porter <mporter@konsulko.com>
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
Subject: Re: [PATCH-v5 1/5] Documentation: binding: add new property 'disable_after_xfer' to i2c-pxa
Date: Wed, 05 Aug 2015 19:54:33 +0530	[thread overview]
Message-ID: <55C21CA1.9040108@linaro.org> (raw)
In-Reply-To: <20150805142011.GC23173@beef>



On Wednesday 05 August 2015 07:50 PM, Matt Porter wrote:
> On Wed, Aug 05, 2015 at 12:04:25PM +0530, Vaibhav Hiremath wrote:
>>
>>
>> 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.
>
> Ahh, ok, thanks...coming in too late on this one. :)
>
>>> 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.
>
> Great, yes, I've always found it hard to follow i2c generic bindings
> since they aren't defined in a clear place like other similar hardware
> (e.g. SPI).
>

Wolfram has already owned up on creating i2c.txt for generic properties.
So, we will be soon close to others.

And thanks for your comments.
Please let me know if you have any other comments on patch-series, so
that I can incorporate it in next version.

Thanks,
Vaibhav

  reply	other threads:[~2015-08-05 14:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 12:41 [PATCH-v5 0/5] i2c: pxa: Add support for PXA910 family of device Vaibhav Hiremath
2015-07-21 12:41 ` [PATCH-v5 1/5] Documentation: binding: add new property 'disable_after_xfer' to i2c-pxa Vaibhav Hiremath
2015-07-27 14:09   ` Matt Porter
2015-08-05  6:34     ` Vaibhav Hiremath
2015-08-05  8:49       ` Wolfram Sang
2015-08-05  9:41         ` Vaibhav Hiremath
2015-08-05 14:24         ` Matt Porter
     [not found]       ` <55C1AE71.3010700-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-05 14:20         ` Matt Porter
2015-08-05 14:24           ` Vaibhav Hiremath [this message]
2015-07-21 12:41 ` [PATCH-v5 2/5] i2c: pxa: enable/disable i2c module across msg xfer Vaibhav Hiremath
     [not found]   ` <1437482466-16126-3-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-05 10:46     ` Shubhrajyoti Datta
     [not found]       ` <CAKfKVtGzDjgHzy70aa0d2W=ROMcxVzerg-qpuB9e4PaGKPpMTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-05 12:42         ` Vaibhav Hiremath
2015-07-21 12:41 ` [PATCH-v5 3/5] i2c: pxa: Add support for pxa910/988 & new configuration features Vaibhav Hiremath
2015-07-21 12:41 ` [PATCH-v5 4/5] Documentation: binding: add sclk adjustment properties to i2c-pxa Vaibhav Hiremath
     [not found]   ` <1437482466-16126-5-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-07-27 14:11     ` Matt Porter
2015-08-05  6:29       ` Vaibhav Hiremath
2015-07-21 12:41 ` [PATCH-v5 5/5] i2c: pxa: Add ILCR (tLow & tHigh) configuration support Vaibhav Hiremath
     [not found]   ` <1437482466-16126-6-git-send-email-vaibhav.hiremath-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-05  8:51     ` Vaibhav Hiremath
     [not found]       ` <55C1CE8E.9000601-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-08-05 19:11         ` Robert Jarzmik
2015-08-06  5:45           ` Vaibhav Hiremath
2015-08-09 12:18         ` Robert Jarzmik
2015-08-09 16:53           ` Vaibhav Hiremath

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C21CA1.9040108@linaro.org \
    --to=vaibhav.hiremath@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mporter@konsulko.com \
    --cc=robert.jarzmik@free.fr \
    --cc=wsa@the-dreams.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).