On Tue, Jun 13, 2017 at 03:47:39PM +0300, Mikko Perttunen wrote: > > > On 13.06.2017 15:46, Mikko Perttunen wrote: > > On 13.06.2017 15:42, Thierry Reding wrote: > > > On Mon, Jun 12, 2017 at 01:23:04PM +0300, Mikko Perttunen wrote: > > > > The Tegra186 CCPLEX_CLUSTER area contains memory-mapped > > > > registers that initiate CPU frequency/voltage transitions. > > > > > > > > Signed-off-by: Mikko Perttunen <mperttunen@xxxxxxxxxx> > > > > Acked-by: Rob Herring <robh@xxxxxxxxxx> > > > > --- > > > > .../arm/tegra/nvidia,tegra186-ccplex-cluster.txt | 20 > > > > ++++++++++++++++++++ > > > > 1 file changed, 20 insertions(+) > > > > create mode 100644 > > > > Documentation/devicetree/bindings/arm/tegra/nvidia,tegra186-ccplex-cluster.txt > > > > > > > > > > The ARM SoC maintainers don't like to pick up device tree bindings, so > > > I'd prefer this to go through the cpufreq tree that also contains the > > > driver patches. Presumably this wasn't merged through that tree because > > > of the missing Acked-by by a device tree maintainer? Given that Rob's > > > acked it now, maybe you can resend this to Viresh, who I think had > > > picked up the driver? > > > > Sure, I'll do that. > > > I guess the .dts change should then also go in that > > way? > > Or I guess not, since you applied it :) So the rule of thumb is that .dts changes should go through ARM SoC and device tree binding changes should be going through the same tree as the driver changes that implement the binding. Thierry
Attachment:
signature.asc
Description: PGP signature
