From: saravanan sekar <sravanhome@gmail.com>
To: Axel Lin <axel.lin@ingics.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: regulator: mpq7920: Some inconsistencies in current driver
Date: Tue, 14 Jan 2020 18:44:57 +0100 [thread overview]
Message-ID: <673bbb3e-70e1-db4e-239e-3fedbbfdd5ad@gmail.com> (raw)
In-Reply-To: <CAFRkauBRi2g_4b3wUnmwLkeogTyWjX4=6VfyDLJr-REf=LeC-w@mail.gmail.com>
On 14/01/20 1:49 pm, Axel Lin wrote:
> Hi Saravanan,
>
> There are a few inconsistencies in current driver:
> I don't have the datasheet, so I'm not 100% sure.
> Maybe you can help check it.
>
> 1. It's unlikely MPQ7920_LDO1_REG_B and MPQ7920_REG_CTL0 have the same address.
> I think this needs double check.
There is no REG_B register for MPQ7920_LDO1, it is a tweak for MACRO expansion consistence of MPQ7920LDO.
However LDO1 doesn't not access this register since mpq7920_ldortc_ops discharge api is set to NULL
> 2. The MPQ7920_DISCHARGE_ON seems wrong because it does not match
> MPQ7920_MASK_DISCHARGE.
> I guess MPQ7920_DISCHARGE_ON should be BIT(5).
Yes, you are correct and thanks for pointing out
>
> 3. The MPQ7920_MASK_BUCK_ILIM seems wrong. I guess it should be 0xC0.
Yes, you are correct and thanks for pointing out
> 4. Not sure why define both MPQ7920_REG_REGULATOR_EN1 and
> MPQ7920_REG_REGULATOR_EN.
There is EN1 register exist but later decided that cannot be handled by
driver so its stray which
shall be removed.
>
> Regards,
> Axel
Thanks,
Saravanan
prev parent reply other threads:[~2020-01-14 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 12:49 regulator: mpq7920: Some inconsistencies in current driver Axel Lin
2020-01-14 17:44 ` saravanan sekar [this message]
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=673bbb3e-70e1-db4e-239e-3fedbbfdd5ad@gmail.com \
--to=sravanhome@gmail.com \
--cc=axel.lin@ingics.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.