[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFBinCDv2m_0tP+rdT1tgXhMs-hPE_cJ9TmO8h9ftDvJXvby+g@mail.gmail.com>
Date: Thu, 19 Sep 2019 22:03:38 +0200
From: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
To: Jianxin Pan <jianxin.pan@...ogic.com>
Cc: Kevin Hilman <khilman@...libre.com>,
linux-amlogic@...ts.infradead.org,
Zhiqiang Liang <zhiqiang.liang@...ogic.com>,
Rob Herring <robh+dt@...nel.org>,
Neil Armstrong <narmstrong@...libre.com>,
Jerome Brunet <jbrunet@...libre.com>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, Jian Hu <jian.hu@...ogic.com>,
Hanjie Lin <hanjie.lin@...ogic.com>,
Victor Wan <victor.wan@...ogic.com>,
Xingyu Chen <xingyu.chen@...ogic.com>
Subject: Re: [PATCH 2/3] soc: amlogic: Add support for Secure power domains controller
Hi Jianxin,
I added three comments below from a quick glance at this driver (I
didn't have time for a complete review)
On Thu, Sep 19, 2019 at 2:11 PM Jianxin Pan <jianxin.pan@...ogic.com> wrote:
[...]
> + pm_genpd_init(&dom->base, NULL,
> + (match->domains[i].get_power ?
> + match->domains[i].get_power(dom) : true));
.get_power is never NULL in this driver so the ": true" part is
effectively a no-op
[...]
> +static const struct of_device_id meson_secure_pwrc_match_table[] = {
> + {
> + .compatible = "amlogic,meson-a1-pwrc",
> + .data = &meson_secure_a1_pwrc_data,
> + },
> + { }
many drivers use a /* sentinel */ comment inside { }
[...]
> +arch_initcall_sync(meson_secure_pwrc_init);
why arch_initcall_sync instead of builtin_platform_driver?
$ grep -R arch_initcall_sync drivers/soc/
$
Martin
Powered by blists - more mailing lists