From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
Alessandro Zummo <a.zummo@towertech.it>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH 1/5] rtc: s5m: Fix register updating by adding regmap for RTC
Date: Tue, 26 Nov 2013 15:26:12 +0100 [thread overview]
Message-ID: <1385475972.30026.3.camel@AMDC1943> (raw)
In-Reply-To: <CAMuHMdWdu2TsvUwmJ4rk3xhMXn4L7MQxdTWRvt80hNttt2sAfA@mail.gmail.com>
On Tue, 2013-11-26 at 15:07 +0100, Geert Uytterhoeven wrote:
> On Tue, Nov 26, 2013 at 2:50 PM, Krzysztof Kozlowski
> <k.kozlowski@samsung.com> wrote:
> > On S5M8767A registers were not properly updated and read due to usage of
> > the same regmap as the PMIC. This could be observed in various hangs,
> > e.g. in infinite loop during waiting for UDR field change.
> >
> > On this chip family the RTC has different I2C address than PMIC so
> > additional regmap is needed.
> >
> > Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > ---
> > drivers/mfd/sec-core.c | 14 ++++++++++++++
> > drivers/rtc/rtc-s5m.c | 2 +-
> > include/linux/mfd/samsung/core.h | 1 +
> > 3 files changed, 16 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mfd/sec-core.c b/drivers/mfd/sec-core.c
> > index 34c18fb..a1a413a 100644
> > --- a/drivers/mfd/sec-core.c
> > +++ b/drivers/mfd/sec-core.c
> > @@ -166,6 +166,11 @@ static struct regmap_config s5m8767_regmap_config = {
> > .cache_type = REGCACHE_FLAT,
> > };
> >
> > +static struct regmap_config sec_rtc_regmap_config = {
>
> const please
Sure.
> > --- a/include/linux/mfd/samsung/core.h
> > +++ b/include/linux/mfd/samsung/core.h
> > @@ -40,6 +40,7 @@ struct sec_pmic_dev {
> > struct device *dev;
> > struct sec_platform_data *pdata;
> > struct regmap *regmap;
> > + struct regmap *regmap_rtc;
>
> Do you think it makes sense to rename the plain "regmap" to "regmap_pmic"?
Yes, I think it would make the code more readable. I'll change it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2013-11-26 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:50 [PATCH 0/5] rtc: s5m: Bug fixes of the driver after tests Krzysztof Kozlowski
2013-11-26 13:50 ` [PATCH 1/5] rtc: s5m: Fix register updating by adding regmap for RTC Krzysztof Kozlowski
2013-11-26 14:07 ` Geert Uytterhoeven
2013-11-26 14:26 ` Krzysztof Kozlowski [this message]
2013-11-26 13:50 ` [PATCH 2/5] rtc: s5m: Fix unsuccesful IRQ request during probe Krzysztof Kozlowski
2013-11-26 13:50 ` [PATCH 3/5] rtc: s5m: Limit endless loop waiting for register update Krzysztof Kozlowski
2013-11-26 13:50 ` [PATCH 4/5] mfd: sec: Add PM ops and make it a wake up source Krzysztof Kozlowski
2013-11-27 12:03 ` Lee Jones
2013-11-26 13:50 ` [PATCH 5/5] rtc: s5m: Enable IRQ wake during suspend Krzysztof Kozlowski
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=1385475972.30026.3.camel@AMDC1943 \
--to=k.kozlowski@samsung.com \
--cc=a.zummo@towertech.it \
--cc=geert@linux-m68k.org \
--cc=kyungmin.park@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.com \
/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