Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1205524 > unrolled thread

Re: [PATCH v4 0/4] clk: hisilicon: support stub clock

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v4 0/4] clk: hisilicon: support stub clock Stephen Boyd <sboyd@codeaurora.org> - 2015-08-12 02:40 +0200
    Re: [PATCH v4 0/4] clk: hisilicon: support stub clock Leo Yan <leo.yan@linaro.org> - 2015-08-12 04:00 +0200
      Re: [PATCH v4 0/4] clk: hisilicon: support stub clock Wei Xu <xuwei5@hisilicon.com> - 2015-08-12 11:30 +0200

#1205524 — Re: [PATCH v4 0/4] clk: hisilicon: support stub clock

On 08/04, Leo Yan wrote:
> This series adds support for hisilicon stub clock driver. On hi6220,
> the bootloader needs load the firmware image and set info for OPPs;
> after run into kernel, the stub clock driver is used to communicate
> w/t firmware for cpu dynamic frequency scaling.
> 
> In patch series v1/v2, the stub clock driver simply writes request in
> sram and send ipc to firmware; For patch series v3, the firmware has
> been upgraded to use mailbox, so stub clock driver will call standard
> mailbox APIs to request mailbox channel and send message to firmware.
> 
> Patch 4 adds stub clock node into dts and it references mailbox with
> phandle, so patch 4 will depend on mailbox driver's patch series [1].
> These patches have been tested on 96board hikey and is used by cpufreq
> driver.

The To: list is everyone, so I'm not sure who is supposed to
apply these patches. I'd like to take patches 1, 2, and 3 through
the clk tree though.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1205549

Hi Stephen,

On Tue, Aug 11, 2015 at 05:38:17PM -0700, Stephen Boyd wrote:
> On 08/04, Leo Yan wrote:
> > This series adds support for hisilicon stub clock driver. On hi6220,
> > the bootloader needs load the firmware image and set info for OPPs;
> > after run into kernel, the stub clock driver is used to communicate
> > w/t firmware for cpu dynamic frequency scaling.
> > 
> > In patch series v1/v2, the stub clock driver simply writes request in
> > sram and send ipc to firmware; For patch series v3, the firmware has
> > been upgraded to use mailbox, so stub clock driver will call standard
> > mailbox APIs to request mailbox channel and send message to firmware.
> > 
> > Patch 4 adds stub clock node into dts and it references mailbox with
> > phandle, so patch 4 will depend on mailbox driver's patch series [1].
> > These patches have been tested on 96board hikey and is used by cpufreq
> > driver.
> 
> The To: list is everyone, so I'm not sure who is supposed to
> apply these patches. I'd like to take patches 1, 2, and 3 through
> the clk tree though.

Thanks, you could take first three patches. For patch 4, i will
re-send it after mailbox driver's patches have been merged.

Wei Xu, is this okay for you?

Thanks,
Leo Yan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1205777

On 8/12/2015 2:49 AM, Leo Yan wrote:
> Hi Stephen,
> 
> On Tue, Aug 11, 2015 at 05:38:17PM -0700, Stephen Boyd wrote:
>> On 08/04, Leo Yan wrote:
>>> This series adds support for hisilicon stub clock driver. On hi6220,
>>> the bootloader needs load the firmware image and set info for OPPs;
>>> after run into kernel, the stub clock driver is used to communicate
>>> w/t firmware for cpu dynamic frequency scaling.
>>>
>>> In patch series v1/v2, the stub clock driver simply writes request in
>>> sram and send ipc to firmware; For patch series v3, the firmware has
>>> been upgraded to use mailbox, so stub clock driver will call standard
>>> mailbox APIs to request mailbox channel and send message to firmware.
>>>
>>> Patch 4 adds stub clock node into dts and it references mailbox with
>>> phandle, so patch 4 will depend on mailbox driver's patch series [1].
>>> These patches have been tested on 96board hikey and is used by cpufreq
>>> driver.
>>
>> The To: list is everyone, so I'm not sure who is supposed to
>> apply these patches. I'd like to take patches 1, 2, and 3 through
>> the clk tree though.
> 
> Thanks, you could take first three patches. For patch 4, i will
> re-send it after mailbox driver's patches have been merged.

Hi Leo,

> Wei Xu, is this okay for you?

OK :)

Best Regards,
Wei

> 
> Thanks,
> Leo Yan
> 
> .
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web