From: Scott Wood <scottwood@freescale.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: fbdev: fsl: fix kernel crash when diu_ops is not implemented
Date: Tue, 24 Nov 2015 16:15:28 +0000 [thread overview]
Message-ID: <1448381728.27264.337.camel@freescale.com> (raw)
In-Reply-To: <1448346450-47403-1-git-send-email-dongsheng.wang@freescale.com>
On Tue, 2015-11-24 at 11:12 -0500, Timur Tabi wrote:
> On Tue, Nov 24, 2015 at 1:27 AM, Dongsheng Wang
> <dongsheng.wang@freescale.com> wrote:
> > @@ -1697,6 +1700,9 @@ static int fsl_diu_probe(struct platform_device
> > *pdev)
> > unsigned int i;
> > int ret;
> >
> > + if (!diu_ops.set_pixel_clock)
> > + return -ENODEV;
> > +
> > data = dmam_alloc_coherent(&pdev->dev, sizeof(struct
> > fsl_diu_data),
> > &dma_addr, GFP_DMA | __GFP_ZERO);
> > if (!data)
>
> This doesn't make any sense. If set_pixel_clock() is not defined,
> then the whole driver aborts the probe.
That's what this patch is trying to accomplish. Currently it crashes instead.
> When could that ever happen?
> If the platform code does not exist, then don't let the driver be
> probed.
How do you propose to accomplish that other than with such a check?
-Scott
next prev parent reply other threads:[~2015-11-24 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 6:27 [PATCH] video: fbdev: fsl: fix kernel crash when diu_ops is not implemented Dongsheng Wang
2015-11-24 10:46 ` Tomi Valkeinen
2015-11-24 11:01 ` Wang Dongsheng
2015-11-24 16:04 ` Timur Tabi
2015-11-24 16:12 ` Timur Tabi
2015-11-24 16:15 ` Scott Wood [this message]
2015-11-24 16:15 ` Tomi Valkeinen
2015-11-24 16:54 ` Timur Tabi
2015-11-24 16:55 ` Scott Wood
2015-11-24 16:56 ` Timur Tabi
2015-11-24 16:57 ` Wang Dongsheng
2015-11-24 16:59 ` Scott Wood
2015-11-24 17:00 ` Scott Wood
2015-11-24 17:02 ` Timur Tabi
2015-11-24 17:02 ` Wang Dongsheng
2015-11-24 17:05 ` Timur Tabi
2015-11-24 17:05 ` Scott Wood
2015-11-24 17:06 ` Timur Tabi
2015-11-24 17:10 ` Scott Wood
2015-11-24 17:16 ` Timur Tabi
2015-11-24 17:17 ` Scott Wood
2015-12-01 8:43 ` Wang Dongsheng
2015-12-01 14:53 ` Timur Tabi
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=1448381728.27264.337.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-fbdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).