linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Tony Lindgren <tony@atomide.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Cc: linux-omap@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod
Date: Thu, 14 Jan 2016 09:44:37 +0200	[thread overview]
Message-ID: <569751E5.40204@ti.com> (raw)
In-Reply-To: <20160113232230.GQ12600@atomide.com>


[-- Attachment #1.1: Type: text/plain, Size: 2094 bytes --]

Hi Tony,

On 14/01/16 01:22, Tony Lindgren wrote:
> Hi,
> 
> * Dan Carpenter <dan.carpenter@oracle.com> [151223 23:29]:
>> [ It's weird that I'm just now getting this warning from 2014...  Oh
>> well, looks legit. -dan ]
> 
> Sorry for the delay on this one, got distracted few times with
> other bugs to deal with. This seems like a valid warning yeah.
> 
> Tomi, do we really need two copies of the the same panels
> files in kernel?
> 
> For example:
> 
> $ find . -name panel-sharp-ls037v7dw01.c
> ./drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c
> ./drivers/video/fbdev/omap2/omapfb/displays/panel-sharp-ls037v7dw01.c

Strictly no, but I think this is the best way forward. Longer story:
http://comments.gmane.org/gmane.comp.video.dri.devel/143151

>> The patch 9522f9fe86f9: "OMAPDSS: panel-sharp-ls037v7dw01: update to
>> use gpiod" from Apr 28, 2014, leads to the following static checker
>> warning:
>>
>> 	drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c:213 sharp_ls_get_gpio()
>> 	warn: 'gd' isn't an ERR_PTR
>>
>> drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c
>>    200  static int sharp_ls_get_gpio(struct device *dev, int gpio, unsigned long flags,
>>    201                    char *desc, struct gpio_desc **gpiod)
>>    202  {
>>    203          struct gpio_desc *gd;
>>    204          int r;
>>    205  
>>    206          *gpiod = NULL;
>>    207  
>>    208          r = devm_gpio_request_one(dev, gpio, flags, desc);
>>    209          if (r)
>>    210                  return r == -ENOENT ? 0 : r;
>>    211  
>>    212          gd = gpio_to_desc(gpio);
>>    213          if (IS_ERR(gd))
>>    214                  return PTR_ERR(gd) == -ENOENT ? 0 : PTR_ERR(gd);
>>                                ^^^^^^^^^^^^^^^^^^^^^^
>> gd can be an ERR_PTR if gpio_to_desc is defined out but it's never
>> -ENOENT.
> 
> Seems like we can just remove the check for -ENOENT here.

Yep. Writing a patch for this and the other panel-sharp-ls037v7dw01
error Dan reported is on my todo.

 Tomi


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-01-14  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151224072926.GE29642@mwanda>
2016-01-13 23:22 ` OMAPDSS: panel-sharp-ls037v7dw01: update to use gpiod Tony Lindgren
2016-01-14  7:44   ` Tomi Valkeinen [this message]
2016-01-14 16:45     ` Tony Lindgren

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=569751E5.40204@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=dan.carpenter@oracle.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-omap@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).