From: Matthias Brugger <matthias.bgg@gmail.com>
To: James Liao <jamesjj.liao@mediatek.com>
Cc: Daniel Kurtz <djkurtz@chromium.org>,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
srv_heupstream <srv_heupstream@mediatek.com>,
Kevin Hilman <khilman@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
Shunli Wang <shunli.wang@mediatek.com>,
Sascha Hauer <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/4] soc: mediatek: Add MT2701/MT7623 scpsys driver
Date: Fri, 8 Jan 2016 12:26:29 +0100 [thread overview]
Message-ID: <568F9CE5.7040601@gmail.com> (raw)
In-Reply-To: <1451971439.19026.3.camel@mtksdaap41>
On 05/01/16 06:23, James Liao wrote:
> Hi Matthias,
> On Wed, 2015-12-30 at 18:49 +0100, Matthias Brugger wrote:
>>> On Wed, 2015-12-30 at 17:01 +0800, Daniel Kurtz wrote:
>>>> On Wed, Dec 30, 2015 at 2:41 PM, James Liao <jamesjj.liao@mediatek.com> wrote:
>>>>>
>>>>> From: Shunli Wang <shunli.wang@mediatek.com>
>>>>>
>>>>> Add scpsys driver for MT2701 and MT7623.
>>>>>
>>>>> Signed-off-by: Shunli Wang <shunli.wang@mediatek.com>
>>>>> Signed-off-by: James Liao <jamesjj.liao@mediatek.com>
>>>>> ---
>>>>> drivers/soc/mediatek/Kconfig | 11 +++
>>>>> drivers/soc/mediatek/Makefile | 1 +
>>>>> drivers/soc/mediatek/mtk-scpsys-mt2701.c | 161 +++++++++++++++++++++++++++++++
>>>>> 3 files changed, 173 insertions(+)
>>>>> create mode 100644 drivers/soc/mediatek/mtk-scpsys-mt2701.c
>>>>>
>>>>> diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
>>>>> index eca6fb7..92cf838 100644
>>>>> --- a/drivers/soc/mediatek/Kconfig
>>>>> +++ b/drivers/soc/mediatek/Kconfig
>>>>> @@ -39,3 +39,14 @@ config MTK_SCPSYS_MT8173
>>>>> driver.
>>>>> The System Control Processor System (SCPSYS) has several power
>>>>> management related tasks in the system.
>>>>> +
>>>>> +config MTK_SCPSYS_MT2701
>>>>> + bool "SCPSYS Support MediaTek MT2701 and MT7623"
>>>>> + depends on ARCH_MEDIATEK || COMPILE_TEST
>>>>> + select MTK_SCPSYS
>>>>> + default ARCH_MEDIATEK
>>>>> + help
>>>>> + Say yes here to add support for the MT2701/MT7623 SCPSYS power
>>>>> + domain driver.
>>>>> + The System Control Processor System (SCPSYS) has several power
>>>>> + management related tasks in the system.
>>>>
>>>> I don't think we really want different drivers and Kconfig options.
>>>>
>>>> Can we just use different compatibles to select the appropriate scp_domain_data?
>>>
>>> Yes, we can. All scpsys drivers are built-in by default, and they will
>>> be activate by specific compatible string.
>>>
>>> But some projects don't want to build unused drivers into kernel to save
>>> code size. Use different Kconfig options for each SoC so that these
>>> projects can disable unused drivers.
>>>
>>
>> Scpsys is a bool right now, you can disable it if you don't need it for
>> your project.
>>
>> I don't think the impact of adding scp_domain_data justifies adding SoC
>> specific scpsys drivers and bloat the drivers/soc/mediatek folder.
>
> So you prefer to enable MT8173 and MT2701 scpsys drivers at the same
> time if MTK_SCPSYS is true?
Well the driver gets enabled by the compatible string from the DT
binding passed to the system. But yes, I prefer to have the code shared
and just add the necessary data structures.
>
> BTW, this patchset is based on 4.4-rc7, which lacks two patches from
> your v4.4-next/soc. Should I rebase to v4.4-next/soc when I send v2
> patch?
>
That would be a nice to have.
Thanks,
Matthias
WARNING: multiple messages have this Message-ID (diff)
From: matthias.bgg@gmail.com (Matthias Brugger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] soc: mediatek: Add MT2701/MT7623 scpsys driver
Date: Fri, 8 Jan 2016 12:26:29 +0100 [thread overview]
Message-ID: <568F9CE5.7040601@gmail.com> (raw)
In-Reply-To: <1451971439.19026.3.camel@mtksdaap41>
On 05/01/16 06:23, James Liao wrote:
> Hi Matthias,
> On Wed, 2015-12-30 at 18:49 +0100, Matthias Brugger wrote:
>>> On Wed, 2015-12-30 at 17:01 +0800, Daniel Kurtz wrote:
>>>> On Wed, Dec 30, 2015 at 2:41 PM, James Liao <jamesjj.liao@mediatek.com> wrote:
>>>>>
>>>>> From: Shunli Wang <shunli.wang@mediatek.com>
>>>>>
>>>>> Add scpsys driver for MT2701 and MT7623.
>>>>>
>>>>> Signed-off-by: Shunli Wang <shunli.wang@mediatek.com>
>>>>> Signed-off-by: James Liao <jamesjj.liao@mediatek.com>
>>>>> ---
>>>>> drivers/soc/mediatek/Kconfig | 11 +++
>>>>> drivers/soc/mediatek/Makefile | 1 +
>>>>> drivers/soc/mediatek/mtk-scpsys-mt2701.c | 161 +++++++++++++++++++++++++++++++
>>>>> 3 files changed, 173 insertions(+)
>>>>> create mode 100644 drivers/soc/mediatek/mtk-scpsys-mt2701.c
>>>>>
>>>>> diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
>>>>> index eca6fb7..92cf838 100644
>>>>> --- a/drivers/soc/mediatek/Kconfig
>>>>> +++ b/drivers/soc/mediatek/Kconfig
>>>>> @@ -39,3 +39,14 @@ config MTK_SCPSYS_MT8173
>>>>> driver.
>>>>> The System Control Processor System (SCPSYS) has several power
>>>>> management related tasks in the system.
>>>>> +
>>>>> +config MTK_SCPSYS_MT2701
>>>>> + bool "SCPSYS Support MediaTek MT2701 and MT7623"
>>>>> + depends on ARCH_MEDIATEK || COMPILE_TEST
>>>>> + select MTK_SCPSYS
>>>>> + default ARCH_MEDIATEK
>>>>> + help
>>>>> + Say yes here to add support for the MT2701/MT7623 SCPSYS power
>>>>> + domain driver.
>>>>> + The System Control Processor System (SCPSYS) has several power
>>>>> + management related tasks in the system.
>>>>
>>>> I don't think we really want different drivers and Kconfig options.
>>>>
>>>> Can we just use different compatibles to select the appropriate scp_domain_data?
>>>
>>> Yes, we can. All scpsys drivers are built-in by default, and they will
>>> be activate by specific compatible string.
>>>
>>> But some projects don't want to build unused drivers into kernel to save
>>> code size. Use different Kconfig options for each SoC so that these
>>> projects can disable unused drivers.
>>>
>>
>> Scpsys is a bool right now, you can disable it if you don't need it for
>> your project.
>>
>> I don't think the impact of adding scp_domain_data justifies adding SoC
>> specific scpsys drivers and bloat the drivers/soc/mediatek folder.
>
> So you prefer to enable MT8173 and MT2701 scpsys drivers at the same
> time if MTK_SCPSYS is true?
Well the driver gets enabled by the compatible string from the DT
binding passed to the system. But yes, I prefer to have the code shared
and just add the necessary data structures.
>
> BTW, this patchset is based on 4.4-rc7, which lacks two patches from
> your v4.4-next/soc. Should I rebase to v4.4-next/soc when I send v2
> patch?
>
That would be a nice to have.
Thanks,
Matthias
next prev parent reply other threads:[~2016-01-08 11:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 6:41 [PATCH 0/4] Mediatek MT2701 SCPSYS power domain support James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` James Liao
[not found] ` <1451457706-14798-1-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 6:41 ` [PATCH 1/4] soc: mediatek: Separate scpsys driver common code James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 10:08 ` James Liao
2015-12-30 10:08 ` James Liao
2015-12-30 10:08 ` James Liao
2015-12-30 6:41 ` [PATCH 2/4] soc: mediatek: Init MT8173 scpsys driver earlier James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` James Liao
[not found] ` <1451457706-14798-3-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 8:52 ` Arnd Bergmann
2015-12-30 10:12 ` James Liao
2015-12-30 10:12 ` James Liao
2015-12-30 10:12 ` James Liao
2015-12-30 10:35 ` Arnd Bergmann
2015-12-30 10:35 ` Arnd Bergmann
2015-12-31 5:59 ` James Liao
2015-12-31 5:59 ` James Liao
2015-12-31 5:59 ` James Liao
2015-12-31 9:16 ` James Liao
2015-12-31 9:16 ` James Liao
2015-12-31 9:16 ` James Liao
2015-12-31 14:45 ` Arnd Bergmann
2015-12-31 14:45 ` Arnd Bergmann
2016-01-04 2:52 ` James Liao
2016-01-04 2:52 ` James Liao
2016-01-04 2:52 ` James Liao
2015-12-30 6:41 ` [PATCH 3/4] soc: mediatek: Add MT2701 power dt-bindings James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` [PATCH 4/4] soc: mediatek: Add MT2701/MT7623 scpsys driver James Liao
2015-12-30 6:41 ` James Liao
2015-12-30 6:41 ` James Liao
[not found] ` <1451457706-14798-5-git-send-email-jamesjj.liao-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2015-12-30 9:01 ` Daniel Kurtz
2015-12-30 9:01 ` Daniel Kurtz
2015-12-30 9:01 ` Daniel Kurtz
2015-12-30 10:18 ` James Liao
2015-12-30 10:18 ` James Liao
2015-12-30 17:49 ` Matthias Brugger
2015-12-30 17:49 ` Matthias Brugger
2015-12-30 17:49 ` Matthias Brugger
2016-01-05 5:23 ` James Liao
2016-01-05 5:23 ` James Liao
2016-01-08 11:26 ` Matthias Brugger [this message]
2016-01-08 11:26 ` 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=568F9CE5.7040601@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=jamesjj.liao@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=shunli.wang@mediatek.com \
--cc=srv_heupstream@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.