linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: Mark Brown <broonie@kernel.org>, Andreas Kemnade <andreas@kemnade.info>
Cc: lgirdwood@gmail.com, linux-kernel@vger.kernel.org, phh@phh.me,
	b.galvani@gmail.com
Subject: Re: [PATCH] regulator: rn5t618: fix rc5t619 ldo10 enable
Date: Thu, 14 Nov 2019 13:13:47 +0100	[thread overview]
Message-ID: <25f0d55696be463def622a37a1f2b826@agner.ch> (raw)
In-Reply-To: <20191114115430.GA4664@sirena.co.uk>

On 2019-11-14 12:54, Mark Brown wrote:
> On Wed, Nov 13, 2019 at 08:26:33PM +0100, Andreas Kemnade wrote:
>> Mark Brown <broonie@kernel.org> wrote:
> 
>> > This definitely looks like a bug but without a datasheet or testing it's
>> > worrying guessing at the register bit to use for the enable for the
>> > second LDO...
> 
>> I am hoping for a Tested-By: from the one who has submitted the patch
>> for the regulator.
> 
> Or a reviewed-by from someone with access to the datasheet.
> 

I guess Pierre-Hugues should have access, as he introduced the part?

>> Well, it is not just guessing, it is there in the url I referenced. But
>> I would of course prefer a better source. At first I wanted to spread
>> my findings.
> 
> The URL you provided looked to be for a different part though?
> 
>> I am not pushing anyone to accept it without Tested-By/Reviewed-Bys.
>> What is a good way to avoid people bumping into this bug?
>> Maybe I can find the right C on the board to check.
> 
> That'd be good.  Or we could fix it by just removing enable/disable
> control for the second LDO entirely and if someone needs that control
> they can always re-add it.

We use the RN5T567 and I added support for it. Unfortunately I have no
access to the RN5T618 datasheet so I cannot tell. The RN5T567 has both
bits in marked reserved, but looking at how it the enable bit are
distributed otherwise this patch fixes it in the only way it makes
sense...

--
Stefan

  reply	other threads:[~2019-11-14 12:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13 18:26 [PATCH] regulator: rn5t618: fix rc5t619 ldo10 enable Andreas Kemnade
2019-11-13 18:32 ` Mark Brown
2019-11-13 19:26   ` Andreas Kemnade
2019-11-14 11:54     ` Mark Brown
2019-11-14 12:13       ` Stefan Agner [this message]
2019-11-14 14:30         ` Andreas Kemnade
2019-11-14 14:24       ` Andreas Kemnade
2019-11-14 19:08         ` Mark Brown
2019-11-20  7:46 ` Pierre-Hugues Husson
2019-11-20 17:18 ` Applied "regulator: rn5t618: fix rc5t619 ldo10 enable" to the regulator tree Mark Brown

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=25f0d55696be463def622a37a1f2b826@agner.ch \
    --to=stefan@agner.ch \
    --cc=andreas@kemnade.info \
    --cc=b.galvani@gmail.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phh@phh.me \
    /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).