From: Sudeep Holla <sudeep.holla@arm.com>
To: Sujeet Kumar Baranwal <sbaranwal@marvell.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [EXT] Re: SCMI & Devfreq
Date: Mon, 16 Sep 2019 11:15:05 +0100 [thread overview]
Message-ID: <20190916101505.GB6109@bogus> (raw)
In-Reply-To: <BYAPR18MB2438723658EF1F0586170CDDAF8C0@BYAPR18MB2438.namprd18.prod.outlook.com>
On Mon, Sep 16, 2019 at 05:22:02AM +0000, Sujeet Kumar Baranwal wrote:
> Thanks Sudeep.
>
>>> Good, but just a quick question to check if this is ACPI or DT based
>>> platform ?
>
> DT based.
>
Good.
>>> Yes it needs some work and I do have some prototype, but with no users in
>>> the upstream, I haven't added it yet.
>>> What kind of devices are these ? There was some work around generic
>>> devfreq driver that I had seen >>on the list and my plan was to do
>>> something similar, I need to dig up details as it was while ago.
>
> These are devices needing dedicated clocks like dsp engines. There is a need
> for a userspace dev governor controlling the frequency in different
> situation.
Okay, thanks for the info.
> Could you please share your patches and any instructions if needed.
>
It needs some polishing before I post them externally, they are still
hackish. I will do soonish.
--
Regards,
Sudeep
_______________________________________________
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:[~2019-09-16 10:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR18MB24387C9DDE32067F1763B6DEAFB00@BYAPR18MB2438.namprd18.prod.outlook.com>
2019-09-13 10:23 ` SCMI & Devfreq Sudeep Holla
2019-09-16 5:22 ` [EXT] " Sujeet Kumar Baranwal
2019-09-16 10:15 ` Sudeep Holla [this message]
2019-09-16 17:36 ` Sujeet Kumar Baranwal
2019-09-18 22:53 ` Sujeet Kumar Baranwal
2019-09-19 15:23 ` Sudeep Holla
2019-09-19 15:23 ` Sudeep Holla
2019-10-07 18:20 ` Sujeet Kumar Baranwal
2019-10-07 18:20 ` Sujeet Kumar Baranwal
2019-10-14 16:58 ` Sudeep Holla
2019-10-14 16:58 ` Sudeep Holla
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=20190916101505.GB6109@bogus \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=sbaranwal@marvell.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.