linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
	linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] omapfb: dss: Handle return error in dss_init_ports.
Date: Thu, 09 Feb 2017 10:14:58 +0000	[thread overview]
Message-ID: <ef0e2b40-b0c9-aa86-fe99-2edd23daa155@gmail.com> (raw)
In-Reply-To: <1645625.BTpumnS8aX@amdc3058>

Hi,
Yes, We will have to handle cleanup of partially initialized ports.
As per your suggestion, I have done the changes.

Thanks
-Arvind

On Wednesday 08 February 2017 07:51 PM, Bartlomiej Zolnierkiewicz wrote:
> On Wednesday, February 08, 2017 11:25:47 AM Bartlomiej Zolnierkiewicz wrote:
>> Hi,
>>
>> On Tuesday, February 07, 2017 05:41:37 PM Arvind Yadav wrote:
>>> Hi,
>>>
>>> In dss_init_ports, There is no need to add dss_uninit_ports before
>>> returning.
>>> Because it's already take care in dss_bind. dss_bind  is handling
>>> dss_uninit_ports in error path.
>> It doesn't handle cleanup of partially initialized ports,
> BTW by "partially initialized ports" here I mean cases like
> i.e. dpi port fully initialized and sdi one not initialized
>
>> please look at the code:
>>
>> ...
>> 	r = dss_init_ports(pdev);
>> 	if (r)
>> 		goto err_init_ports;
>> ...
>> err_runtime_get:
>> 	pm_runtime_disable(&pdev->dev);
>> 	dss_uninit_ports(pdev);
>> err_init_ports:
>> 	if (dss.video1_pll)
>> 		dss_video_pll_uninit(dss.video1_pll);
>> ...
>>
>> dss_uninit_ports() is not called on partially initialized
> ditto
>
>> ports (when dss_init_ports() returns an error we go straight
>> into err_init_ports label and skip dss_uninit_ports())
>>
>>> -Arvind
>>>
>>>
>>> On Monday 06 February 2017 08:58 PM, Bartlomiej Zolnierkiewicz wrote:
>>>> dpi_uninit_port() & sdi_uninit_port() skip not fully
>>>> initialized port
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
>


      reply	other threads:[~2017-02-09 10:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170203122444epcas2p3e0d5ed32cac85fd86d900a62dbeb03a4@epcas2p3.samsung.com>
2017-02-03 12:35 ` [PATCH] omapfb: dss: Handle return error in dss_init_ports Arvind Yadav
2017-02-06 15:28   ` Bartlomiej Zolnierkiewicz
2017-02-07 12:23     ` Arvind Yadav
2017-02-08 10:25       ` Bartlomiej Zolnierkiewicz
2017-02-08 14:21         ` Bartlomiej Zolnierkiewicz
2017-02-09 10:14           ` Arvind Yadav [this message]

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=ef0e2b40-b0c9-aa86-fe99-2edd23daa155@gmail.com \
    --to=arvind.yadav.cs@gmail.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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).