Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Chanwoo Choi <cw00.choi@samsung.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: myungjoo.ham@samsung.com, kyungmin.park@samsung.com,
	lukasz.luba@arm.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 3/3] PM / devfreq: event: Change prototype of devfreq_event_get_edev_by_phandle function
Date: Mon, 14 Sep 2020 09:15:39 +0900	[thread overview]
Message-ID: <6ed7a604-d10d-c2e1-34cf-d22b6fa083f8@samsung.com> (raw)
In-Reply-To: <20200910120812.GC2206@pi3>

On 9/10/20 9:08 PM, Krzysztof Kozlowski wrote:
> On Tue, Sep 08, 2020 at 07:24:47PM +0900, Chanwoo Choi wrote:
>> Previously, devfreq core support 'devfreq-events' property in order to get
>> the devfreq-event device by phandle. But, 'devfreq-events' property name is
>> not proper on devicetree binding because this name doesn't mean
>> the any h/w attribute.
>>
>> The devfreq-event core hand over the rights to decide the property name
>> for getting the devfreq-event device on devicetree. Each devfreq-event driver
>> will decide the property name on devicetree binding and then pass
>> the their own property name to devfreq_event_get_edev_by_phandle function.
>>
>> And change the prototype of devfreq_event_get_edev_count function
>> because of used deprecated 'devfreq-events' property.
>>
>> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
>> ---
>>  drivers/devfreq/devfreq-event.c         | 14 ++++++++------
>>  drivers/devfreq/exynos-bus.c            |  5 +++--
>>  drivers/devfreq/rk3399_dmc.c            |  2 +-
>>  drivers/memory/samsung/exynos5422-dmc.c |  6 ++++--
>>  include/linux/devfreq-event.h           | 14 ++++++++++----
>>  5 files changed, 26 insertions(+), 15 deletions(-)
>>
> 
> Feel free to take it via devfreq tree. I don't expect conflicts around
> memory/samsung/exynos5422-dmc.c.
> 
> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
> 

Thanks for review. Applied them to devfreq-next.

-- 
Best Regards,
Chanwoo Choi
Samsung Electronics

      reply	other threads:[~2020-09-14  0:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200908101230epcas1p321249119f81d90755efdfafd95f9d180@epcas1p3.samsung.com>
2020-09-08 10:24 ` [PATCH v3 0/3] PM / devfreq: Deprecate fixed property name by using phandle get Chanwoo Choi
2020-09-08 10:24   ` [PATCH v3 1/3] PM / devfreq: Add devfreq_get_devfreq_by_node function Chanwoo Choi
2020-09-10 12:05     ` Krzysztof Kozlowski
2020-09-08 10:24   ` [PATCH v3 2/3] PM / devfreq: Change prototype of devfreq_get_devfreq_by_phandle function Chanwoo Choi
2020-09-10 12:06     ` Krzysztof Kozlowski
2020-09-08 10:24   ` [PATCH v3 3/3] PM / devfreq: event: Change prototype of devfreq_event_get_edev_by_phandle function Chanwoo Choi
2020-09-10 12:08     ` Krzysztof Kozlowski
2020-09-14  0:15       ` Chanwoo Choi [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=6ed7a604-d10d-c2e1-34cf-d22b6fa083f8@samsung.com \
    --to=cw00.choi@samsung.com \
    --cc=krzk@kernel.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=myungjoo.ham@samsung.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