From: Ladislav Michl <ladis@linux-mips.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: Andreas Kemnade <andreas@kemnade.info>,
David Rivshin <drivshin@allworx.com>,
linux-pwm@vger.kernel.org,
linux-omap <linux-omap@vger.kernel.org>,
Tony Lindgren <tony@atomide.com>, Keerthy <j-keerthy@ti.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: [PATCH] pwm: pwm-omap-dmtimer: fix probing problems by returning EPROBE_DEFER
Date: Sun, 29 Jul 2018 20:08:04 +0200 [thread overview]
Message-ID: <20180729180804.GA18468@lenoch> (raw)
In-Reply-To: <BE83C4E8-55B0-4EA7-8FF6-756460464264@goldelico.com>
On Sun, Jul 29, 2018 at 08:32:41AM +0200, H. Nikolaus Schaller wrote:
> Hi,
>
> > Am 28.07.2018 um 22:35 schrieb Ladislav Michl <ladis@linux-mips.org>:
> >
> > Hi Andreas,
> >
> > On Sat, Jul 28, 2018 at 06:59:14PM +0200, Andreas Kemnade wrote:
> >> I got this in the kernel log:
> >> [ 0.756042] omap-dmtimer-pwm dmtimer-pwm: dmtimer pdata structure NULL
> >> [ 0.756134] omap-dmtimer-pwm: probe of dmtimer-pwm failed with error -22
> >>
> >> the probe function has to wait until omap_dm_timer_probe() in
> >> clocksource/timer-ti-dm.c has initialized pdata, so defer probing
> >
> > There already is a patch by David Rivshin addressing the same issue...
>
> Here it is:
>
> https://patchwork.ozlabs.org/patch/943148/
>
> but hasn't arrived in linux-next.
That's because there'll be v3.
> But it is questionable if a driver should dev_info() about doing deferred probing.
> IMHO, it should just do it which is how Andreas' patch works.
See here: https://patchwork.ozlabs.org/patch/949659/
> >> Fixes: b7290cf6ff78 (pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops)
> >> Signed-off-by: Andreas Kemnade <andreas@kemnade.info>
> >> ---
> >> drivers/pwm/pwm-omap-dmtimer.c | 3 +--
> >> 1 file changed, 1 insertion(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/pwm/pwm-omap-dmtimer.c b/drivers/pwm/pwm-omap-dmtimer.c
> >> index 665da3c8fbce..808835179c2e 100644
> >> --- a/drivers/pwm/pwm-omap-dmtimer.c
> >> +++ b/drivers/pwm/pwm-omap-dmtimer.c
> >> @@ -264,8 +264,7 @@ static int pwm_omap_dmtimer_probe(struct platform_device *pdev)
> >>
> >> timer_pdata = dev_get_platdata(&timer_pdev->dev);
> >> if (!timer_pdata) {
> >> - dev_err(&pdev->dev, "dmtimer pdata structure NULL\n");
> >> - ret = -EINVAL;
> >> + ret = -EPROBE_DEFER;
> >> goto put;
> >> }
> >>
> >> --
> >> 2.11.0
> >>
>
> BR,
> Nikolaus
>
next prev parent reply other threads:[~2018-07-29 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 16:59 [PATCH] pwm: pwm-omap-dmtimer: fix probing problems by returning EPROBE_DEFER Andreas Kemnade
2018-07-28 20:35 ` Ladislav Michl
2018-07-29 6:32 ` H. Nikolaus Schaller
2018-07-29 18:08 ` Ladislav Michl [this message]
2018-07-29 18:19 ` H. Nikolaus Schaller
2018-07-30 22:56 ` David Rivshin
2018-07-31 6:35 ` H. Nikolaus Schaller
2018-07-31 14:35 ` David Rivshin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180729180804.GA18468@lenoch \
--to=ladis@linux-mips.org \
--cc=andreas@kemnade.info \
--cc=drivshin@allworx.com \
--cc=hns@goldelico.com \
--cc=j-keerthy@ti.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox