linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: okaya@codeaurora.org
To: Srinath Mannam <srinath.mannam@broadcom.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-clk@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi-owner@vger.kernel.org
Subject: Re: ACPI support in common clock framework
Date: Thu, 14 Jun 2018 07:07:47 -0400	[thread overview]
Message-ID: <977a6d1c83b4084b949162258bb1007a@codeaurora.org> (raw)
In-Reply-To: <CABe79T5i8zUcBJnFmM-pAvzXf2CZXesh4NqxSGFj8f0Z-c8m1g@mail.gmail.com>

On 2018-06-14 06:58, Srinath Mannam wrote:
> Thank you Andy,
> 
> Regards,
> Srinath.
> 
> On Wed, Jun 13, 2018 at 1:43 PM, Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
>> +Cc: Rafael, ACPI ML
>> 
>> On Wed, Jun 13, 2018 at 7:14 AM, Srinath Mannam
>> <srinath.mannam@broadcom.com> wrote:
>>> Hi Michael, Stephen,
>>> 
>>> We are adding ACPI support in our Linux based platform.
>>> At present our clock hierarchy using common clock framework through 
>>> DTS.
>>> Now we required ACPI support in common clock framework to upgrade our 
>>> platform.
>>> 
>>> For example, clk_get API called in many drivers to get clock device 
>>> is
>>> tightly coupled with DT framework.
>>> 
>>> Please let us know, if anybody in Open Source community have plans to
>>> add ACPI support for common clock framework.
>>> If not please suggest us alternative method to use common clock
>>> framework in ACPI use case.

Are you hooking up clk apis to PS0/PS3 calls?

Clk api didn't play nice with acpi until now.

>>> 
>>> Thanks in advance.
>>> 
>>> Regards,
>>> Srinath.
>> 
>> 
>> 
>> --
>> With Best Regards,
>> Andy Shevchenko
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" 
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2018-06-14 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABe79T6zQ_7Ycws5b=xaQ3edpVn1QPQyWd9p24eqLGpYbdtt0A@mail.gmail.com>
2018-06-13  8:13 ` ACPI support in common clock framework Andy Shevchenko
2018-06-13  8:27   ` Rafael J. Wysocki
2018-06-15 17:43     ` Stephen Boyd
2018-06-16 15:50       ` Rafael J. Wysocki
2018-06-25 16:37         ` Stephen Boyd
2018-06-25 17:15           ` Sudeep Holla
2018-06-25 23:37             ` Stephen Boyd
2018-06-26  8:59               ` Srinath Mannam
2018-06-26 17:27               ` Andy Shevchenko
2018-06-14 10:58   ` Srinath Mannam
2018-06-14 11:07     ` okaya [this message]

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=977a6d1c83b4084b949162258bb1007a@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=linux-acpi-owner@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@kernel.org \
    --cc=srinath.mannam@broadcom.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).