[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1548987217.28835.2.camel@mtksdaap41>
Date: Fri, 1 Feb 2019 10:13:37 +0800
From: Hsin-hsiung Wang <hsin-hsiung.wang@...iatek.com>
To: Mark Brown <broonie@...nel.org>
CC: Mark Rutland <mark.rutland@....com>, <devicetree@...r.kernel.org>,
<srv_heupstream@...iatek.com>, Liam Girdwood <lgirdwood@...il.com>,
<linux-kernel@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
<linux-mediatek@...ts.infradead.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Lee Jones <lee.jones@...aro.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 5/6] regulator: mt6358: Add support for MT6358 regulator
Hi Mark,
On Wed, 2019-01-30 at 15:18 +0000, Mark Brown wrote:
> On Wed, Jan 30, 2019 at 05:18:10PM +0800, Hsin-Hsiung Wang wrote:
>
> > +static const struct of_device_id mt6358_of_match[] = {
> > + { .compatible = "mediatek,mt6358-regulator", },
> > + { /* sentinel */ },
> > +};
> > +MODULE_DEVICE_TABLE(of, mt6358_of_match);
>
> There should be no need for a separate compatbile string here - we
> aren't describing the hardware any more than we already did with the
> parent node for the MFD, we're describing how Linux currently splits the
> software that controls the hardware up. Just have the MFD instantiate
> the regulator driver when it probes.
>
> Otherwise this driver looks very good and clean.
Thanks for your suggestion.
It sounds pretty good and I will modify it in next patch series.
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
Powered by blists - more mailing lists