From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Alessandro Zummo <a.zummo@towertech.it>,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
Marek Szyprowski <m.szyprowski@samsung.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 1/5] mfd/rtc: s5m: Fix register updating by adding regmap for RTC
Date: Fri, 29 Nov 2013 09:04:29 +0000 [thread overview]
Message-ID: <20131129090429.GA26086@lee--X1> (raw)
In-Reply-To: <1385626183-22990-2-git-send-email-k.kozlowski@samsung.com>
On Thu, 28 Nov 2013, Krzysztof Kozlowski wrote:
> Rename old regmap field of "struct sec_pmic_dev" to "regmap_pmic" and
> add new regmap for RTC.
>
> 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 | 30 ++++++++++++++++++++++--------
> drivers/mfd/sec-irq.c | 6 +++---
> drivers/regulator/s5m8767.c | 2 +-
> drivers/rtc/rtc-s5m.c | 2 +-
> include/linux/mfd/samsung/core.h | 3 ++-
> 5 files changed, 29 insertions(+), 14 deletions(-)
The MFD parts look fine to me. I just need the Acks from the other
maintainers before I can apply it:
Acked-by: Lee Jones <lee.jones@lianro.org>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-11-29 9:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 8:09 [PATCH v2 0/5] rtc: s5m: Bug fixes of the driver after tests Krzysztof Kozlowski
2013-11-28 8:09 ` [PATCH v2 1/5] mfd/rtc: s5m: Fix register updating by adding regmap for RTC Krzysztof Kozlowski
2013-11-28 13:50 ` Mark Brown
2013-11-29 0:08 ` Sangbeom Kim
2013-11-29 9:04 ` Lee Jones [this message]
2013-11-28 8:09 ` [PATCH v2 2/5] rtc: s5m: Fix unsuccesful IRQ request during probe Krzysztof Kozlowski
2013-11-28 13:46 ` Mark Brown
2013-11-29 0:10 ` Sangbeom Kim
2013-11-28 8:09 ` [PATCH v2 3/5] rtc: s5m: Limit endless loop waiting for register update Krzysztof Kozlowski
2013-11-28 13:47 ` Mark Brown
2013-11-29 0:13 ` Sangbeom Kim
2013-11-28 8:09 ` [PATCH v2 4/5] rtc: s5m: Enable IRQ wake during suspend Krzysztof Kozlowski
2013-11-29 0:15 ` Sangbeom Kim
2013-11-28 8:09 ` [PATCH v2 5/5] mfd: sec: Constify regmap configs and regmap irqs Krzysztof Kozlowski
2013-11-28 17:14 ` Mark Brown
2013-11-29 0:18 ` Sangbeom Kim
2013-11-29 8:53 ` Lee Jones
2013-12-02 23:10 ` [PATCH v2 0/5] rtc: s5m: Bug fixes of the driver after tests Andrew Morton
2013-12-03 8:34 ` 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=20131129090429.GA26086@lee--X1 \
--to=lee.jones@linaro.org \
--cc=a.zummo@towertech.it \
--cc=broonie@kernel.org \
--cc=geert@linux-m68k.org \
--cc=k.kozlowski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--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