From: Kevin Hilman <khilman@baylibre.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
krzk+dt@kernel.org
Cc: matthias.bgg@gmail.com, jia-wei.chang@mediatek.com,
roger.lu@mediatek.com, hsinyi@google.com,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V2 10/15] cpufreq: mediatek: Make sram regulator optional
Date: Thu, 14 Apr 2022 10:20:01 -0700 [thread overview]
Message-ID: <7hfsmf37lq.fsf@baylibre.com> (raw)
In-Reply-To: <be86691b529dd691203fbb5b35f8572e7e9119a8.camel@mediatek.com>
Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
> On Fri, 2022-04-08 at 13:32 -0700, Kevin Hilman wrote:
>> Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
>>
>> > From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>> >
>> > For some MediaTek SoCs, like MT8186, it's possible that the sram
>> > regulator
>> > is shared between CPU and CCI.
>> >
>> > Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>>
>> nit: missing your sign-off.
>>
>> > ---
>> > drivers/cpufreq/mediatek-cpufreq.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/cpufreq/mediatek-cpufreq.c
>> > b/drivers/cpufreq/mediatek-cpufreq.c
>> > index 9e9bce0ff235..8f688d47e64b 100644
>> > --- a/drivers/cpufreq/mediatek-cpufreq.c
>> > +++ b/drivers/cpufreq/mediatek-cpufreq.c
>> > @@ -435,7 +435,7 @@ static int mtk_cpu_dvfs_info_init(struct
>> > mtk_cpu_dvfs_info *info, int cpu)
>> > }
>> >
>> > /* Both presence and absence of sram regulator are valid cases.
>> > */
>> > - info->sram_reg = regulator_get_exclusive(cpu_dev, "sram");
>> > + info->sram_reg = regulator_get_optional(cpu_dev, "sram");
>>
>> The changelog says that this regulator may be shared with CCI, so I
>> understand it's no longer exclusive. But here you make it optional,
>> which should be explained in the changelog. If it's not actually
>> optional, then it should just be normal "get".
>>
>> Kevin
>
> Hello Kevin,
>
> Since cpufreq and cci devfreq might share the same sram regulator in
> MediaTek SoC, it is no longer exclusive as you mentioned.
>
> The reason to use regulator_get_optional is we hope regulator framework
> can return error for error handling rather than a dummy handler from
> regulator_get api.
>
> I will add this to commit message in next version.
OK, sounds good.
Thanks,
Kevin
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
krzk+dt@kernel.org
Cc: matthias.bgg@gmail.com, jia-wei.chang@mediatek.com,
roger.lu@mediatek.com, hsinyi@google.com,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V2 10/15] cpufreq: mediatek: Make sram regulator optional
Date: Thu, 14 Apr 2022 10:20:01 -0700 [thread overview]
Message-ID: <7hfsmf37lq.fsf@baylibre.com> (raw)
In-Reply-To: <be86691b529dd691203fbb5b35f8572e7e9119a8.camel@mediatek.com>
Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
> On Fri, 2022-04-08 at 13:32 -0700, Kevin Hilman wrote:
>> Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
>>
>> > From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>> >
>> > For some MediaTek SoCs, like MT8186, it's possible that the sram
>> > regulator
>> > is shared between CPU and CCI.
>> >
>> > Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>>
>> nit: missing your sign-off.
>>
>> > ---
>> > drivers/cpufreq/mediatek-cpufreq.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/cpufreq/mediatek-cpufreq.c
>> > b/drivers/cpufreq/mediatek-cpufreq.c
>> > index 9e9bce0ff235..8f688d47e64b 100644
>> > --- a/drivers/cpufreq/mediatek-cpufreq.c
>> > +++ b/drivers/cpufreq/mediatek-cpufreq.c
>> > @@ -435,7 +435,7 @@ static int mtk_cpu_dvfs_info_init(struct
>> > mtk_cpu_dvfs_info *info, int cpu)
>> > }
>> >
>> > /* Both presence and absence of sram regulator are valid cases.
>> > */
>> > - info->sram_reg = regulator_get_exclusive(cpu_dev, "sram");
>> > + info->sram_reg = regulator_get_optional(cpu_dev, "sram");
>>
>> The changelog says that this regulator may be shared with CCI, so I
>> understand it's no longer exclusive. But here you make it optional,
>> which should be explained in the changelog. If it's not actually
>> optional, then it should just be normal "get".
>>
>> Kevin
>
> Hello Kevin,
>
> Since cpufreq and cci devfreq might share the same sram regulator in
> MediaTek SoC, it is no longer exclusive as you mentioned.
>
> The reason to use regulator_get_optional is we hope regulator framework
> can return error for error handling rather than a dummy handler from
> regulator_get api.
>
> I will add this to commit message in next version.
OK, sounds good.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Rex-BC Chen <rex-bc.chen@mediatek.com>,
rafael@kernel.org, viresh.kumar@linaro.org, robh+dt@kernel.org,
krzk+dt@kernel.org
Cc: matthias.bgg@gmail.com, jia-wei.chang@mediatek.com,
roger.lu@mediatek.com, hsinyi@google.com,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH V2 10/15] cpufreq: mediatek: Make sram regulator optional
Date: Thu, 14 Apr 2022 10:20:01 -0700 [thread overview]
Message-ID: <7hfsmf37lq.fsf@baylibre.com> (raw)
In-Reply-To: <be86691b529dd691203fbb5b35f8572e7e9119a8.camel@mediatek.com>
Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
> On Fri, 2022-04-08 at 13:32 -0700, Kevin Hilman wrote:
>> Rex-BC Chen <rex-bc.chen@mediatek.com> writes:
>>
>> > From: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>> >
>> > For some MediaTek SoCs, like MT8186, it's possible that the sram
>> > regulator
>> > is shared between CPU and CCI.
>> >
>> > Signed-off-by: Jia-Wei Chang <jia-wei.chang@mediatek.com>
>>
>> nit: missing your sign-off.
>>
>> > ---
>> > drivers/cpufreq/mediatek-cpufreq.c | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/drivers/cpufreq/mediatek-cpufreq.c
>> > b/drivers/cpufreq/mediatek-cpufreq.c
>> > index 9e9bce0ff235..8f688d47e64b 100644
>> > --- a/drivers/cpufreq/mediatek-cpufreq.c
>> > +++ b/drivers/cpufreq/mediatek-cpufreq.c
>> > @@ -435,7 +435,7 @@ static int mtk_cpu_dvfs_info_init(struct
>> > mtk_cpu_dvfs_info *info, int cpu)
>> > }
>> >
>> > /* Both presence and absence of sram regulator are valid cases.
>> > */
>> > - info->sram_reg = regulator_get_exclusive(cpu_dev, "sram");
>> > + info->sram_reg = regulator_get_optional(cpu_dev, "sram");
>>
>> The changelog says that this regulator may be shared with CCI, so I
>> understand it's no longer exclusive. But here you make it optional,
>> which should be explained in the changelog. If it's not actually
>> optional, then it should just be normal "get".
>>
>> Kevin
>
> Hello Kevin,
>
> Since cpufreq and cci devfreq might share the same sram regulator in
> MediaTek SoC, it is no longer exclusive as you mentioned.
>
> The reason to use regulator_get_optional is we hope regulator framework
> can return error for error handling rather than a dummy handler from
> regulator_get api.
>
> I will add this to commit message in next version.
OK, sounds good.
Thanks,
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-14 17:20 UTC|newest]
Thread overview: 217+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 4:58 [PATCH V2 00/15] cpufreq: mediatek: Cleanup and support MT8183 and MT8186 Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` [PATCH V2 01/15] dt-bindings: cpufreq: mediatek: Add MediaTek CCI property Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 8:10 ` Krzysztof Kozlowski
2022-04-08 8:10 ` Krzysztof Kozlowski
2022-04-08 8:10 ` Krzysztof Kozlowski
2022-04-08 10:24 ` Rex-BC Chen
2022-04-08 10:24 ` Rex-BC Chen
2022-04-08 10:24 ` Rex-BC Chen
2022-04-08 11:49 ` Krzysztof Kozlowski
2022-04-08 11:49 ` Krzysztof Kozlowski
2022-04-08 11:49 ` Krzysztof Kozlowski
2022-04-11 6:48 ` Rex-BC Chen
2022-04-11 6:48 ` Rex-BC Chen
2022-04-11 6:48 ` Rex-BC Chen
2022-04-08 4:58 ` [PATCH V2 02/15] cpufreq: mediatek: Use module_init and add module_exit Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 3:17 ` Viresh Kumar
2022-04-11 3:17 ` Viresh Kumar
2022-04-11 3:17 ` Viresh Kumar
2022-04-08 4:58 ` [PATCH V2 03/15] cpufreq: mediatek: Cleanup variables and error handling in mtk_cpu_dvfs_info_init() Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 3:20 ` Viresh Kumar
2022-04-11 3:20 ` Viresh Kumar
2022-04-11 3:20 ` Viresh Kumar
2022-04-08 4:58 ` [PATCH V2 04/15] cpufreq: mediatek: Remove unused headers Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 3:21 ` Viresh Kumar
2022-04-11 3:21 ` Viresh Kumar
2022-04-11 3:21 ` Viresh Kumar
2022-04-08 4:58 ` [PATCH V2 05/15] cpufreq: mediatek: Enable clocks and regulators Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 3:22 ` Viresh Kumar
2022-04-11 3:22 ` Viresh Kumar
2022-04-11 3:22 ` Viresh Kumar
2022-04-08 4:58 ` [PATCH V2 06/15] cpufreq: mediatek: Record previous target vproc value Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 4:58 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 11:35 ` Rex-BC Chen
2022-04-11 11:35 ` Rex-BC Chen
2022-04-11 11:35 ` Rex-BC Chen
2022-04-11 3:26 ` Viresh Kumar
2022-04-11 3:26 ` Viresh Kumar
2022-04-11 3:26 ` Viresh Kumar
2022-04-11 11:33 ` Rex-BC Chen
2022-04-11 11:33 ` Rex-BC Chen
2022-04-11 11:33 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 07/15] cpufreq: mediatek: Add opp notification for SVS support Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 11:31 ` Rex-BC Chen
2022-04-11 11:31 ` Rex-BC Chen
2022-04-08 20:29 ` Kevin Hilman
2022-04-08 20:29 ` Kevin Hilman
2022-04-08 20:29 ` Kevin Hilman
2022-04-11 11:29 ` Rex-BC Chen
2022-04-11 11:29 ` Rex-BC Chen
2022-04-11 18:09 ` Kevin Hilman
2022-04-11 18:09 ` Kevin Hilman
2022-04-11 18:09 ` Kevin Hilman
2022-04-12 8:18 ` Rex-BC Chen
2022-04-12 8:18 ` Rex-BC Chen
2022-04-12 18:04 ` Kevin Hilman
2022-04-12 18:04 ` Kevin Hilman
2022-04-12 18:04 ` Kevin Hilman
2022-04-13 11:21 ` Rex-BC Chen
2022-04-13 11:21 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 08/15] cpufreq: mediatek: Move voltage limits to platform data Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-08 13:36 ` AngeloGioacchino Del Regno
2022-04-11 11:18 ` Rex-BC Chen
2022-04-11 11:18 ` Rex-BC Chen
2022-04-11 11:18 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 09/15] cpufreq: mediatek: Add .get function Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 10/15] cpufreq: mediatek: Make sram regulator optional Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 20:32 ` Kevin Hilman
2022-04-08 20:32 ` Kevin Hilman
2022-04-08 20:32 ` Kevin Hilman
2022-04-14 10:53 ` Rex-BC Chen
2022-04-14 10:53 ` Rex-BC Chen
2022-04-14 10:53 ` Rex-BC Chen
2022-04-14 17:20 ` Kevin Hilman [this message]
2022-04-14 17:20 ` Kevin Hilman
2022-04-14 17:20 ` Kevin Hilman
2022-04-08 4:59 ` [PATCH V2 11/15] cpufreq: mediatek: Update logic of voltage_tracking() Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 21:08 ` Kevin Hilman
2022-04-08 21:08 ` Kevin Hilman
2022-04-08 21:08 ` Kevin Hilman
2022-04-14 11:30 ` Rex-BC Chen
2022-04-14 11:30 ` Rex-BC Chen
2022-04-14 11:30 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 12/15] cpufreq: mediatek: Use maximum voltage in init stage Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-12 11:24 ` Rex-BC Chen
2022-04-12 11:24 ` Rex-BC Chen
2022-04-12 11:24 ` Rex-BC Chen
2022-04-14 3:40 ` Rex-BC Chen
2022-04-14 3:40 ` Rex-BC Chen
2022-04-14 3:40 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 13/15] cpufreq: mediatek: Link CCI device to CPU Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-11 11:50 ` Rex-BC Chen
2022-04-11 11:50 ` Rex-BC Chen
2022-04-11 11:50 ` Rex-BC Chen
2022-04-08 20:54 ` Kevin Hilman
2022-04-08 20:54 ` Kevin Hilman
2022-04-08 20:54 ` Kevin Hilman
2022-04-11 11:51 ` Rex-BC Chen
2022-04-11 11:51 ` Rex-BC Chen
2022-04-11 11:51 ` Rex-BC Chen
2022-04-11 12:31 ` Rex-BC Chen
2022-04-11 12:31 ` Rex-BC Chen
2022-04-11 12:31 ` Rex-BC Chen
2022-04-11 18:13 ` Kevin Hilman
2022-04-11 18:13 ` Kevin Hilman
2022-04-11 18:13 ` Kevin Hilman
2022-04-12 12:26 ` Rex-BC Chen
2022-04-12 12:26 ` Rex-BC Chen
2022-04-12 12:26 ` Rex-BC Chen
2022-04-12 18:50 ` Kevin Hilman
2022-04-12 18:50 ` Kevin Hilman
2022-04-12 18:50 ` Kevin Hilman
2022-04-13 11:32 ` Rex-BC Chen
2022-04-13 11:32 ` Rex-BC Chen
2022-04-13 11:32 ` Rex-BC Chen
2022-04-13 21:41 ` Kevin Hilman
2022-04-13 21:41 ` Kevin Hilman
2022-04-13 21:41 ` Kevin Hilman
2022-04-14 2:32 ` Rex-BC Chen
2022-04-14 2:32 ` Rex-BC Chen
2022-04-14 2:32 ` Rex-BC Chen
2022-04-14 21:48 ` Kevin Hilman
2022-04-14 21:48 ` Kevin Hilman
2022-04-14 21:48 ` Kevin Hilman
2022-04-15 2:31 ` Rex-BC Chen
2022-04-15 2:31 ` Rex-BC Chen
2022-04-15 2:31 ` Rex-BC Chen
2022-04-19 18:16 ` Kevin Hilman
2022-04-19 18:16 ` Kevin Hilman
2022-04-19 18:16 ` Kevin Hilman
2022-04-08 4:59 ` [PATCH V2 14/15] cpufreq: mediatek: Add support for MT8186 Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 21:10 ` Kevin Hilman
2022-04-08 21:10 ` Kevin Hilman
2022-04-08 21:10 ` Kevin Hilman
2022-04-11 11:14 ` Rex-BC Chen
2022-04-11 11:14 ` Rex-BC Chen
2022-04-11 11:14 ` Rex-BC Chen
2022-04-08 4:59 ` [PATCH V2 15/15] cpufreq: mediatek: Use device print to show logs Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 4:59 ` Rex-BC Chen
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-08 13:37 ` AngeloGioacchino Del Regno
2022-04-11 3:29 ` Viresh Kumar
2022-04-11 3:29 ` Viresh Kumar
2022-04-11 3:29 ` Viresh Kumar
2022-04-11 11:09 ` Rex-BC Chen
2022-04-11 11:09 ` Rex-BC Chen
2022-04-11 11:09 ` Rex-BC Chen
2022-04-08 21:11 ` [PATCH V2 00/15] cpufreq: mediatek: Cleanup and support MT8183 and MT8186 Kevin Hilman
2022-04-08 21:11 ` Kevin Hilman
2022-04-08 21:11 ` Kevin Hilman
2022-04-09 1:05 ` Hsin-Yi Wang
2022-04-09 1:05 ` Hsin-Yi Wang
2022-04-09 1:05 ` Hsin-Yi Wang
2022-04-11 11:37 ` Rex-BC Chen
2022-04-11 11:37 ` Rex-BC Chen
2022-04-11 11:37 ` Rex-BC Chen
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=7hfsmf37lq.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@google.com \
--cc=jia-wei.chang@mediatek.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=rex-bc.chen@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=roger.lu@mediatek.com \
--cc=viresh.kumar@linaro.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 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.