linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Stephen Boyd <sboyd@kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Rob Herring <robh+dt@kernel.org>,
	matthias.bgg@kernel.org
Cc: mtk01761 <wendell.lin@mediatek.com>,
	devicetree@vger.kernel.org, Allison Randal <allison@lohutok.net>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-mediatek@lists.infradead.org,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] clk/soc: mediatek: mt6779: Bind clock driver from platform device
Date: Wed, 20 May 2020 12:54:18 +0200	[thread overview]
Message-ID: <45fcf31f-918b-fbc6-5c55-5fa74e3a7002@gmail.com> (raw)
In-Reply-To: <158996971719.215346.12802870863066637932@swboyd.mtv.corp.google.com>



On 20/05/2020 12:15, Stephen Boyd wrote:
> Quoting matthias.bgg@kernel.org (2020-05-18 04:31:55)
>> From: Matthias Brugger <matthias.bgg@gmail.com>
>>
>> The mmsys driver is now the top level entry point for the multimedia
>> system (mmsys), we bind the clock driver by creating a platform device.
>> We also bind the MediaTek DRM driver which is not yet implement and
>> therefor will errror out for now.
>>
>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>> ---
> 
> Acked-by: Stephen Boyd <sboyd@kernel.org>
> 

Now queued for v5.7-next/soc


  reply	other threads:[~2020-05-20 10:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 11:31 [PATCH 1/4] clk/soc: mediatek: mt8183: Bind clock driver from platform device matthias.bgg
2020-05-18 11:31 ` [PATCH 2/4] clk/soc: mediatek: mt6797: " matthias.bgg
2020-05-19  0:23   ` Chun-Kuang Hu
2020-05-20 10:15   ` Stephen Boyd
2020-05-20 10:53     ` Matthias Brugger
2020-05-18 11:31 ` [PATCH 3/4] clk/soc: mediatek: mt6779: " matthias.bgg
2020-05-19 15:10   ` Chun-Kuang Hu
2020-05-19 21:26     ` Matthias Brugger
2020-05-19 23:52       ` Chun-Kuang Hu
2020-05-20 10:15   ` Stephen Boyd
2020-05-20 10:54     ` Matthias Brugger [this message]
2020-05-20 10:21   ` Stephen Boyd
2020-05-18 11:31 ` [PATCH 4/4] arm64: dts: mt6797: Fix mmsys node name matthias.bgg
2020-05-19 15:06   ` Chun-Kuang Hu
2020-05-20 10:54     ` Matthias Brugger
2020-05-18 15:30 ` [PATCH 1/4] clk/soc: mediatek: mt8183: Bind clock driver from platform device Chun-Kuang Hu
2020-05-18 15:57   ` Matthias Brugger
2020-05-19  0:21     ` Chun-Kuang Hu
2020-05-20 10:14 ` Stephen Boyd
2020-05-20 10:53   ` 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=45fcf31f-918b-fbc6-5c55-5fa74e3a7002@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=allison@lohutok.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kstewart@linuxfoundation.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=matthias.bgg@kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wendell.lin@mediatek.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;
as well as URLs for NNTP newsgroup(s).