All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: michael.srba@seznam.cz
Cc: Beomho Seo <beomho.seo@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: rt5033: fix errorneous defines
Date: Fri, 13 Nov 2020 10:12:48 +0000	[thread overview]
Message-ID: <20201113101248.GD3718728@dell> (raw)
In-Reply-To: <20201110130047.8097-1-michael.srba@seznam.cz>

On Tue, 10 Nov 2020, michael.srba@seznam.cz wrote:

> From: Michael Srba <Michael.Srba@seznam.cz>
> 
> Fix regulators on rt5033 by converting some values to bitmasks which were 
> errorneously not defined as such in the header file.
> 
> Cc: Beomho Seo <beomho.seo@samsung.com>
> Fixes: 0b271258544b ("mfd: rt5033: Add Richtek RT5033 driver core.")
> Signed-off-by: Michael Srba <Michael.Srba@seznam.cz>
> ---
> 
> Tested on Samsung Galaxy A3 (sm-a3ulte).
> 
> Other areas (e.g "RT5033 use internal timer need to set time") still look
> suspicious, but without access to a datasheet it's unfortunately hard
> to evaluate. Moreover, these values are not currently utilized so it's not
> clear what format would be expected. (it's however hard to argue for
> the removal of said values, since with the datasheet not being publicly
> available, this file may be the best documentation of them)
> 
> ---
>  include/linux/mfd/rt5033-private.h | 28 ++++++++++++++--------------
>  1 file changed, 14 insertions(+), 14 deletions(-)

Applied, thanks.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2020-11-13 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 13:00 [PATCH] mfd: rt5033: fix errorneous defines michael.srba
2020-11-13 10:12 ` Lee Jones [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=20201113101248.GD3718728@dell \
    --to=lee.jones@linaro.org \
    --cc=beomho.seo@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.srba@seznam.cz \
    /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.