Re: [PATCH v6 2/2] arm64: dts: sdm845: Add gpu and gmu device nodes

On 18-12-18, 11:05, Doug Anderson wrote:

OK, it's fine with me to have the fallback, but if we do we should be
consistent about it and make sure it's in all the bindings and device
tree files...

Sure.

I am not sure what's the right way to do it is, i.e. should we keep the
"operating-points-v2" string or not. Another example I see is (which can be
compared here) is the board specific DT files. Normally the root node's
compatible is a long list of strings like:

compatible = "nvidia,p2371-2180", "nvidia,p2180", "nvidia,tegra210";

which starts from platform-specific string, then mach, then board, etc..

We do keep all of them in those cases and that makes me wonder why the same
shouldn't be done for OPP bindings.

-- 
viresh

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

On Tue, Dec 18, 2018 at 10:49 PM Viresh Kumar [off-list ref] wrote:

On 18-12-18, 11:05, Doug Anderson wrote:

quoted

OK, it's fine with me to have the fallback, but if we do we should be
consistent about it and make sure it's in all the bindings and device
tree files...

Sure.

I am not sure what's the right way to do it is, i.e. should we keep the
"operating-points-v2" string or not.

Does having it buy you anything? Given the QCom one doesn't have any
frequency or voltage, I don't see how it would be useful to have it.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel