On 17.09.2019 23:20, Rob Herring wrote: > On Fri, Aug 23, 2019 at 05:36:56PM +0300, Leonard Crestez wrote: >> The interconnect-node-id property is parsed by the imx interconnect >> driver to find nodes on which frequencies can be adjusted. >> >> Add #interconnect-cells so that device drivers can request paths from >> bus nodes instead of requiring a separate "virtual" node to represent >> the interconnect itself. >> >> Signed-off-by: Leonard Crestez <leonard.crestez@xxxxxxx> >> --- >> Documentation/devicetree/bindings/devfreq/imx-ddrc.yaml | 5 +++++ >> Documentation/devicetree/bindings/devfreq/imx.yaml | 5 +++++ >> 2 files changed, 10 insertions(+) > > Please combine this with the other series for devfreq support. I understand that having two series which add to the same bindings file is odd but the devfreq and interconnect parts are independent to a very large degree and devfreq can be useful on it's own. The only reason devfreq bindings are updated is to avoid adding a "virtual" node for interconnect. Since DT is a big source of confusion here can you read https://patchwork.kernel.org/cover/11111865/#22883457 and maybe offer some advice? -- Regards, Leonard
