public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Peter Rosin <peda@axentia.se>, Sebastian Reichel <sre@kernel.org>,
	linux-tegra@vger.kernel.org
Cc: linux-pm@vger.kernel.org
Subject: Re: bq24735 charger and ac-detect
Date: Thu, 15 Dec 2016 14:04:03 +0000	[thread overview]
Message-ID: <721122dd-dda8-1830-9224-40b5ed79e463@nvidia.com> (raw)
In-Reply-To: <bfc89f2f-fbcb-2a04-e679-832fef1f0948@axentia.se>


On 15/12/16 12:04, Peter Rosin wrote:

...

>>                               The only other option is to add another
>> property called something like 'ti,ac-detect-override-pol' to specify
>> the polarity you want.
> 
> How is that helping? It's no different that just saying active-low for
> boards that do not invert ACOK (which is what I currently do in my dts,
> but I hate doing it since it doesn't match dt docs and is therefore just
> wrong).

By providing a means for the user to specify the polarity for their
board. Of course the documentation would need to be updated as well. I
think all solutions will be ugly if we need to preserve compatibility.

>> To be honest, I am not sure how this type of thing is normally handled.
>> So probably best to put together a patch with whatever option you feel
>> best and explain why this is needed and see what the dev-tree folks say.
> 
> I suspect that at the end of the day documentation is less important than
> regressions. But if there are more than one implementation of the same
> spec and Linux is not following it, it's kind of harsh to change the spec
> to match Linux. I doubt that there are any other users in this case though,
> but what do I know?
> 
> I'll send a patch re-documenting ti,ac-detect-gpios to specify AC absence
> instead of AC presence, let's see what the dt people thinks...

Fine with me and of course that works for Tegra, but how does that
ultimately help you? How do you tell the driver to use active-high
instead of the default which is not active-low?

Jon

-- 
nvpublic

  reply	other threads:[~2016-12-15 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d796f6f9-1b6a-647c-100b-b3e85fc2f4c0@axentia.se>
     [not found] ` <20161214142502.su4auesnlqmgxspv@earth>
2016-12-14 14:59   ` bq24735 charger and ac-detect Sebastian Reichel
2016-12-14 17:22     ` Jon Hunter
2016-12-14 17:54     ` Jon Hunter
2016-12-14 21:22       ` Peter Rosin
     [not found]         ` <84ede737-9e4c-b0ba-5a37-a96a7e86c3ec-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-12-15 10:45           ` Jon Hunter
     [not found]             ` <21e09552-96b9-fb72-60be-7a4b9347b761-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-12-15 12:04               ` Peter Rosin
2016-12-15 14:04                 ` Jon Hunter [this message]
     [not found]                   ` <721122dd-dda8-1830-9224-40b5ed79e463-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-12-15 14:07                     ` Jon Hunter
2016-12-15 15:34                     ` Peter Rosin
     [not found]                       ` <1316ab3d-8a75-6a03-e1d0-7dee55f2c90f-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-12-15 16:10                         ` Jon Hunter

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=721122dd-dda8-1830-9224-40b5ed79e463@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=peda@axentia.se \
    --cc=sre@kernel.org \
    /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