On Wed, Nov 03, 2021 at 03:35:08PM -0700, Trent Piepho wrote:
> On Tue, Nov 2, 2021 at 12:40 AM Sascha Hauer <sha@xxxxxxxxxxxxxx> wrote:
> >
> > On Mon, Nov 01, 2021 at 11:33:07AM -0700, Trent Piepho wrote:
> > > On Mon, Nov 1, 2021 at 2:01 AM Sascha Hauer <[1]sha@xxxxxxxxxxxxxx> wrote:
> > >
> > > > The phy is only optional as long as none is specified in the device
> > > > tree. When there is one specified then it's no longer optional. We can't
> > > > do the right thing here without checking the device tree. Given that
> > > > it's simple to enable CONFIG_GENERIC_PHY I think this is the way to go.
> > >
> > > But this force enables GENERIC_PHY when it's not needed.
> > >
> > > There are commonly many device nodes in Linux dts files that are not used
> > > by an enabled Barebox driver. It's normal to turn off a driver that might
> > > be or could be used. Is it necessarily an error if a phy is present in
> > > the dts but we don't wish to include support for it?
> >
> > We need to distinguish the cases "There is a phy specified, but the
> > reset defaults are good enough to go without a driver" and "There is a
> > phy specified and we need driver support for it". barebox can't know
> > this.
>
> Could we say that compiling barebox without CONFIG_GENERIC_PHY means
> the driver is not needed and compiling it with the driver means that
> is it?
Please no. Enabling Kconfig options ideally gives you additional
features, but it should not break anything. Consider the case when you
need to enable CONFIG_GENERIC_PHY for something else like an LVDS phy or
whatever, you don't want to end up with broken USB support then and have
to choose whether USB or LVDS is working.
>
> One can have the defconfig include drivers that might be needed, but
> at some point an engineer ought to be able to
>
> > Returning NULL from the phy_optional_get() stub has another problem:
> > Some devices might work with CONFIG_GENERIC_PHY disabled, but stop
> > to work when CONFIG_GENERIC_PHY gets enabled, because we might have
> > no driver for the phy. Having boards that only work with CONFIG_GENERIC_PHY
> > disabled is rather unexpected as well.
>
> Return NULL if there is no driver.
>
> > > struct phy *phy_optional_get(struct device_d *dev, const char *string)
> > > {
> > > if (dev->device_node &&
> > > !of_parse_phandle_with_args(dev->device_node, "phys",
> > > "#phy-cells", of_property_match_string(dev->device_node, "phy-names",
> > > string), NULL))
> > > dev_warn(dev, "%s phy specified in device tree but
> > > CONFIG_GENERIC_PHY support is not enabled", string);
> > > return NULL;
> > > }
> >
> > I am fine with this approach. We could add a check if the phy node has a
> > status = "disabled" property. That would allow a board to explicitly
> > state that we do not need to support a phy. We could then do the
> > right thing no matter if CONFIG_GENERIC_PHY is enabled or not.
> >
> > Thinking about it I would prefer something like barebox,status = "disabled"
> > to prevent the property from leaking into Linux.
>
> Wouldn't it be easier to just delete the phy-names property to disable the phy?
My point is that you sometimes start Linux with the barebox internal
device tree. We should then pass a device tree Linux can handle
properly. A barebox,status would just be ignored by Linux whereas a
status = "disabled" property or deleted phy-names property would disable
the phy for Linux as well.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
