On Fri 08 Apr 16:01 PDT 2016, Timur Tabi wrote: > Bjorn Andersson wrote: > > >It sounds like you're trying to say that the pins used can be are > >muxed as GPIO or MDIO, in the TLMM. > > I'm not 100% sure, but I think that's correct. If you don't want to have > normal networking, you could connect those external pins to some GPIO device > (like an LED or whatever), and then configure the pin muxing for GPIO > purposes. But if that's true, it's only true on the FSM9900. On the > QDF2432, those lines are not connected to the TLMM. They are instead > hard-wired to the Emac. > Then through proper use of the pinctrl framework you should configure the FSM9900 to mux these pins appropriately and the two solutions are equivalent. > >In the downstream kernel this is often seen with the drivers calling > >gpio_request() to "reserve" said pins, but all you should do is > >described the desired configuration and muxing in the pinctrl node, > >reference that from your driver and simply ignore the fact that those > >pins could have been used as GPIO pins. > > That makes sense, but I think the driver already does that. > > https://patchwork.ozlabs.org/patch/561667/ > > Function emac_probe_resources() has a call to of_get_named_gpio(). And then > emac_mac_up() calls gpio_request(). As far as I can tell, that's it. > > I'm guessing that the of_get_named_gpio() call needs to be changed somehow, > but I'm not sure how. > Thanks for the link. In short those call to the gpio framework should just be removed. They should only be there if you're using the gpiolib to control the state of those pins, and you're not as far as I can see. The general outline of what you should have in your dts instead is: soc { tlmm { compatible = "qcom,pinctrl-xyz"; mdio_pins_a: mdio { state { pins = "gpio0", "gpio1"; function = "mdio"; }; }; }; emac { compatible = "qcom,somthing-emac"; pinctrl-names = "default"; pinctrl-0 = <&mdio_pins_a>; }; }; Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
