All of lore.kernel.org
 help / color / mirror / Atom feed
From: Devendra Talegaonkar <Devendra.Talegaonkar@kpit.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] Add VSP1 devices to DT for r8a7790 and r8a7791
Date: Thu, 05 Feb 2015 00:28:26 +0000	[thread overview]
Message-ID: <1423096093300.88011@kpit.com> (raw)
In-Reply-To: <1410651385-13090-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>

Thanks Laurent for your reply.
The problem we are facing is, we are planning to assign overlay planes to different modules in the system (processes) & depending on the system context we want to decide which overlay plane needs to bring forward and which overlay plane needs to hide. As you suggested in the previous mail,  handling XXSetPlane API would not be a desired option.

Can you please suggest any suitable mechanism for the same?

Thanks & Regards,
Devendra Talegaonkar

________________________________________
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Sent: Wednesday, February 4, 2015 2:50 PM
To: Devendra Talegaonkar
Cc: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] Add VSP1 devices to DT for r8a7790 and r8a7791

Hello,

On Tuesday 03 February 2015 09:41:23 Devendra Talegaonkar wrote:
> Hi Laurent,
>
> This is altogether a different question & not sure if I am doing sense or
> not.
>
> I am trying to access drmModeSetCrtc and drmModeSetPlane from 2 different
> processes. The scenario is:
>
> * Process1 is creating frame buffer for CRTc & for specific plane & by
> calling drmModeSetPlane, overlaying on CRTc
>
> * Process2 is also creating frame buffer for different plane & trying to
> overlay it on CRTc
>
> In the Process2 drmModeSetPlane is not showing anything on display.
>
> Is it the desired behavior or I am doing something wrong here.

That doesn't sound like the desired behaviour to me. Note that KMS expects a
single process to control mode setting. You can get around that by dropping
master privileges in the first process after setting the CRTC mode, but you
can't get master privileges back once you've dropped them (short of dropping
master in the second process and then closing/reopening the device in the
first process of course).

--
Regards,

Laurent Pinchart

This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.

  parent reply	other threads:[~2015-02-05  0:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 23:36 [PATCH 0/2] Add VSP1 devices to DT for r8a7790 and r8a7791 Laurent Pinchart
2014-09-30  4:47 ` Cao Minh Hiep
2014-09-30 22:56 ` Laurent Pinchart
2014-10-01  4:35 ` Cao Minh Hiep
2014-12-09  8:54 ` Devendra Talegaonkar
2014-12-15  3:42 ` Devendra Talegaonkar
2014-12-15 23:49 ` Laurent Pinchart
2014-12-16 23:34 ` Laurent Pinchart
2014-12-19  5:05 ` Devendra Talegaonkar
2014-12-20 19:00 ` Laurent Pinchart
2014-12-20 21:46 ` Sakari Ailus
2014-12-22  9:27 ` Laurent Pinchart
2015-02-04 14:50 ` Laurent Pinchart
2015-02-05  0:28 ` Devendra Talegaonkar [this message]
2015-02-09  8:59 ` Laurent Pinchart

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=1423096093300.88011@kpit.com \
    --to=devendra.talegaonkar@kpit.com \
    --cc=linux-sh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.