From: Matthias Brugger <matthias.bgg@gmail.com>
To: Lee Jones <lee.jones@linaro.org>, matthias.bgg@kernel.org
Cc: ulrich.hecht+renesas@gmail.com,
laurent.pinchart@ideasonboard.com, ck.hu@mediatek.com,
p.zabel@pengutronix.de, airlied@linux.ie, robh+dt@kernel.org,
mark.rutland@arm.com, mturquette@baylibre.com,
sboyd@codeaurora.org, davem@davemloft.net,
gregkh@linuxfoundation.org, mchehab@kernel.org,
rdunlap@infradead.org, pi-cheng.chen@linaro.org,
sean.wang@mediatek.com, linux-clk@vger.kernel.org,
linux@armlinux.org.uk, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Matthias Brugger <mbrugger@suse.com>
Subject: Re: [v2 00/10] arm/arm64: mediatek: Fix mmsys device probing
Date: Tue, 24 Apr 2018 11:46:13 +0200 [thread overview]
Message-ID: <723392d5-ee51-d49b-050b-db4f9709e6bf@gmail.com> (raw)
In-Reply-To: <20180424054854.bpd6h3imazhqnuy3@dell>
Hi Lee,
On 04/24/2018 07:48 AM, Lee Jones wrote:
> On Mon, 23 Apr 2018, matthias.bgg@kernel.org wrote:
>
>> From: Matthias Brugger <mbrugger@suse.com>
>>
>> Changes since v1:
>> - add binding documentation
>> - ddp: use regmap_update_bits
>> - ddp: ignore EPROBE_DEFER on clock probing
>> - mfd: delete mmsys_private
>> - add Reviewed-by and Acked-by tags
>
> I'm confused by the double submission.
>
> Please can you send it again completely detached from the first and
> the second submissions please?
>
I had some problems with my mailclient. I'll resend as 'v2 resend'.
Sorry for that.
Matthias
>> ---
>>
>> MMSYS in Mediatek SoCs has some registers to control clock gates (which is
>> used in the clk driver) and some registers to set the routing and enable
>> the differnet blocks of the display subsystem.
>>
>> Up to now both drivers, clock and drm are probed with the same device tree
>> compatible. But only the first driver get probed, which in effect breaks
>> graphics on mt8173 and mt2701.
>>
>> This patch set introduces a new mfd device, which binds against the mmsys
>> compatible and takes care of probing the needed devices. It was tested on the
>> bananapi-r2 and the Acer R13 Chromebook.
>>
>>
>> Matthias Brugger (10):
>> dt-bindings: mediatek: mmsys: Add support for mfd
>> drm/mediatek: Use regmap for register access
>> mfd: mtk-mmsys: Add mmsys driver
>> drm/mediatek: mt2701: switch to mfd probing.
>> clk: mediatek: mt2701-mm: switch to mfd device
>> mfd: mtk-mmsys: Add mt8173 nodes
>> drm/mediatek: Add mfd support for mt8173
>> clk: mediatek: mt8173-mm: switch to mfd device
>> drm: mediatek: Omit warning on probe defers
>> MAINTAINERS: update Mediatek Soc entry
>>
>> .../bindings/arm/mediatek/mediatek,mmsys.txt | 2 -
>> .../bindings/display/mediatek/mediatek,disp.txt | 2 +-
>> .../devicetree/bindings/mfd/mediatek,mmsys.txt | 27 +++++++
>> MAINTAINERS | 2 +
>> drivers/clk/mediatek/clk-mt2701-mm.c | 10 +--
>> drivers/clk/mediatek/clk-mt8173.c | 17 +++-
>> drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 4 +-
>> drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 41 ++++------
>> drivers/gpu/drm/mediatek/mtk_drm_ddp.h | 4 +-
>> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 33 ++++----
>> drivers/gpu/drm/mediatek/mtk_drm_drv.h | 2 +-
>> drivers/mfd/Kconfig | 9 +++
>> drivers/mfd/Makefile | 2 +
>> drivers/mfd/mtk-mmsys.c | 93 ++++++++++++++++++++++
>> 14 files changed, 189 insertions(+), 59 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/mfd/mediatek,mmsys.txt
>> create mode 100644 drivers/mfd/mtk-mmsys.c
>>
>
prev parent reply other threads:[~2018-04-24 9:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 16:13 [v2 00/10] arm/arm64: mediatek: Fix mmsys device probing matthias.bgg
2018-04-23 16:13 ` [v2 01/10] dt-bindings: mediatek: mmsys: Add support for mfd matthias.bgg
2018-04-23 16:13 ` [v2 02/10] drm/mediatek: Use regmap for register access matthias.bgg
2018-04-23 16:13 ` [v2 03/10] mfd: mtk-mmsys: Add mmsys driver matthias.bgg
2018-04-23 16:13 ` [v2 04/10] drm/mediatek: mt2701: switch to mfd probing matthias.bgg
2018-04-23 16:13 ` [v2 05/10] clk: mediatek: mt2701-mm: switch to mfd device matthias.bgg
2018-04-23 16:13 ` [v2 06/10] mfd: mtk-mmsys: Add mt8173 nodes matthias.bgg
2018-04-23 16:13 ` [v2 07/10] drm/mediatek: Add mfd support for mt8173 matthias.bgg
2018-04-23 16:13 ` [v2 08/10] clk: mediatek: mt8173-mm: switch to mfd device matthias.bgg
2018-04-24 10:05 ` kbuild test robot
2018-04-23 16:13 ` [v2 09/10] drm: mediatek: Omit warning on probe defers matthias.bgg
2018-04-23 16:13 ` [v2 10/10] MAINTAINERS: update Mediatek Soc entry matthias.bgg
2018-04-24 5:48 ` [v2 00/10] arm/arm64: mediatek: Fix mmsys device probing Lee Jones
2018-04-24 9:46 ` Matthias Brugger [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=723392d5-ee51-d49b-050b-db4f9709e6bf@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=airlied@linux.ie \
--cc=ck.hu@mediatek.com \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@kernel.org \
--cc=mbrugger@suse.com \
--cc=mchehab@kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=pi-cheng.chen@linaro.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sean.wang@mediatek.com \
--cc=ulrich.hecht+renesas@gmail.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