[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141215143850.GD13885@x1>
Date: Mon, 15 Dec 2014 14:38:50 +0000
From: Lee Jones <lee.jones@...aro.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...inux.com, a.zummo@...ertech.it,
rtc-linux@...glegroups.com, wim@...ana.be,
linux-watchdog@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 5/8] mfd: Add ST's Low Power Controller driver
On Mon, 15 Dec 2014, Arnd Bergmann wrote:
> On Monday 15 December 2014 13:50:52 Lee Jones wrote:
> > > >
> > >
> > > I don't think it's necessary to have the MFD node if only one of the
> > > two modes can be used based on a DT property. It should be enough
> > > to have both the rtc and the wdt driver list the same compatible
> > > string and check the property in the probe function to decide if
> > > they want to drive the device or not:
> >
> > I tried that and it didn't work. Only one driver probed.
> >
> >
>
> Strange, the code in really_probe() and the comment in device_attach()
> suggest that this is not the intentional behavior. What error
> code did you return? If it's -ENODEV or -ENXIO, it should keep
> trying the other drivers, otherwise it will give up.
Oh I see. So if I return -ENODEV it will keep trying to bind with
other drivers. I'll try that and report back.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists