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@xxxxxxxxxxx> > --- > 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@xxxxxxxxxx> Best regards, Krzysztof
