From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/8] drm/mediatek: Use regmap for register access
Date: Fri, 20 Apr 2018 12:00:19 +0200 [thread overview]
Message-ID: <1524218419.16259.7.camel@pengutronix.de> (raw)
In-Reply-To: <3fffe06c-f19b-ef26-a19d-771611aae158@gmail.com>
Hi Matthias,
On Fri, 2018-04-20 at 11:41 +0200, Matthias Brugger wrote:
> Hi Philipp,
>
> On 11/23/2017 09:54 AM, Philipp Zabel wrote:
> > Hi Matthias,
> >
> > On Tue, 2017-11-14 at 22:41 +0100, Matthias Brugger wrote:
> > > The mmsys memory space is shared between the drm and the
> > > clk driver. Use regmap to access it.
> > >
> > > Signed-off-by: Matthias Brugger <mbrugger@suse.com>
> > > ---
> > > drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 4 ++--
> > > drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 30 +++++++++++++++++-------------
> > > drivers/gpu/drm/mediatek/mtk_drm_ddp.h | 4 ++--
> > > drivers/gpu/drm/mediatek/mtk_drm_drv.c | 13 ++++---------
> > > drivers/gpu/drm/mediatek/mtk_drm_drv.h | 2 +-
> > > 5 files changed, 26 insertions(+), 27 deletions(-)
> >
> > [...]
>
> [...]
> > > }
> > >
> > > value = mtk_ddp_sel_in(cur, next, &addr);
> > > if (value) {
> > > - reg = readl_relaxed(config_regs + addr) & ~value;
> > > - writel_relaxed(reg, config_regs + addr);
> > > + regmap_read(config_regs, addr, ®);
> > > + reg &= ~value;
> > > + regmap_write(config_regs, addr, reg);
> >
> > regmap_update_bits(config_regs, addr, value, 0);
> >
> > Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
> >
>
> Thanks for having a look on that.
>
> I'll update the next version with regmap_update_bits and leave your Reviewed-by,
> hope that's ok.
Yes, that's fine.
regards
Philipp
next prev parent reply other threads:[~2018-04-20 10:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 21:41 [PATCH 0/8] arm/arm64: mediatek: Fix mmsys device probing Matthias Brugger
2017-11-14 21:41 ` [PATCH 1/8] drm/mediatek: Use regmap for register access Matthias Brugger
2017-11-23 5:44 ` CK Hu
2017-11-23 8:54 ` Philipp Zabel
2018-04-20 9:41 ` Matthias Brugger
2018-04-20 10:00 ` Philipp Zabel [this message]
2017-11-14 21:41 ` [PATCH 2/8] mfd: mtk-mmsys: Add mmsys driver Matthias Brugger
2017-11-23 9:04 ` CK Hu
2017-11-23 18:37 ` Matthias Brugger
2017-11-23 9:09 ` Philipp Zabel
2017-11-14 21:41 ` [PATCH 3/8] drm/mediatek: mt2701: switch to mfd probing Matthias Brugger
2017-11-23 5:48 ` CK Hu
2017-11-23 8:30 ` Matthias Brugger
2017-11-23 8:47 ` CK Hu
2017-11-23 9:12 ` Philipp Zabel
2017-11-14 21:41 ` [PATCH 4/8] clk: mediatek: mt2701-mm: switch to mfd device Matthias Brugger
2017-11-15 0:17 ` Stephen Boyd
2018-04-20 13:00 ` Matthias Brugger
2018-04-20 13:04 ` Matthias Brugger
2017-11-14 21:41 ` [PATCH 5/8] mfd: mtk-mmsys: Add mt8173 nodes Matthias Brugger
2017-11-23 9:13 ` Philipp Zabel
2017-11-14 21:41 ` [PATCH 6/8] drm/mediatek: Add mfd support for mt8173 Matthias Brugger
2017-11-23 8:51 ` CK Hu
2017-11-23 9:13 ` Philipp Zabel
2017-11-14 21:41 ` [PATCH 7/8] clk: mediatek: mt8173-mm: switch to mfd device Matthias Brugger
2017-11-15 0:16 ` Stephen Boyd
2017-11-14 21:41 ` [PATCH 8/8] MAINTAINERS: update Mediatek Soc entry Matthias Brugger
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=1524218419.16259.7.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 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).