From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Cc: "linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"xinliang.liu@linaro.org" <xinliang.liu@linaro.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return
Date: Thu, 28 Jan 2016 14:20:37 +0000 [thread overview]
Message-ID: <1453990837.4304.15.camel@synopsys.com> (raw)
In-Reply-To: <56A123CD.1060706@synopsys.com>
SGkgQ2FybG9zLA0KDQpPbiBUaHUsIDIwMTYtMDEtMjEgYXQgMTg6MzAgKzAwMDAsIENhcmxvcyBQ
YWxtaW5oYSB3cm90ZToNCj4gaGkuLi4NCj4gDQo+IGkganVzdCBmb3VuZCB0aGF0IGl0cyBibG9j
a2luZyB3YWl0aW5nIGZvciBjb25zb2xlX2xvY2suLi4NCj4gQHZpbmVldCwgYWxleGV5OiBpIHRo
aW5rIHRoYXQgY29uc29sZV9sb2NrIGlzIGFyY2hpdGVjdHVyZSBkZXBlbmRlbnQgcmlnaHQ/IERv
IHlvdSBrbm93IGFueSBpc3N1ZSB3aXRoIGNvbnNvbGVfbG9jaw0KPiBmb3IgQVJDPw0KDQpJJ20g
bm90IHJlYWxseSBzdXJlICJjb25zb2xlX2xvY2siIGhhcyBzb21ldGhpbmcgdG8gZG8gd2l0aCBB
UkMgYXJjaGl0ZWN0dXJlLg0KQXQgbGVhc3QgImdpdCBncmVwIGJjb25zb2xlX2xvY2siIGRvZXNu
J3QgZmluZCBhbnl0aGluZyBpbiAiYXJjaC9hcmMiLg0KDQpTbyBJJ2QgYXNzdW1lIHRoaXMgaXMg
YSBnZW5lcmljIHRoaW5nLg0KDQotQWxleGV5
WARNING: multiple messages have this Message-ID (diff)
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return
Date: Thu, 28 Jan 2016 14:20:37 +0000 [thread overview]
Message-ID: <1453990837.4304.15.camel@synopsys.com> (raw)
In-Reply-To: <56A123CD.1060706@synopsys.com>
Hi Carlos,
On Thu, 2016-01-21@18:30 +0000, Carlos Palminha wrote:
> hi...
>
> i just found that its blocking waiting for console_lock...
> @vineet, alexey: i think that console_lock is architecture dependent right? Do you know any issue with console_lock
> for ARC?
I'm not really sure "console_lock" has something to do with ARC architecture.
At least "git grep bconsole_lock" doesn't find anything in "arch/arc".
So I'd assume this is a generic thing.
-Alexey
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Cc: "linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"xinliang.liu@linaro.org" <xinliang.liu@linaro.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"tomi.valkeinen@ti.com" <tomi.valkeinen@ti.com>,
"laurent.pinchart@ideasonboard.com"
<laurent.pinchart@ideasonboard.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return
Date: Thu, 28 Jan 2016 14:20:37 +0000 [thread overview]
Message-ID: <1453990837.4304.15.camel@synopsys.com> (raw)
In-Reply-To: <56A123CD.1060706@synopsys.com>
Hi Carlos,
On Thu, 2016-01-21 at 18:30 +0000, Carlos Palminha wrote:
> hi...
>
> i just found that its blocking waiting for console_lock...
> @vineet, alexey: i think that console_lock is architecture dependent right? Do you know any issue with console_lock
> for ARC?
I'm not really sure "console_lock" has something to do with ARC architecture.
At least "git grep bconsole_lock" doesn't find anything in "arch/arc".
So I'd assume this is a generic thing.
-Alexey
next prev parent reply other threads:[~2016-01-28 14:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 18:46 Whats missing in my new FB DRM driver... "No connectors reported connected with modes"? Carlos Palminha
2015-12-30 18:53 ` Carlos Palminha
2015-12-30 18:53 ` Carlos Palminha
2015-12-31 2:19 ` Xinliang Liu
2016-01-18 14:32 ` Carlos Palminha
2016-01-18 14:32 ` Carlos Palminha
2016-01-18 14:45 ` Carlos Palminha
2016-01-18 14:45 ` Carlos Palminha
2016-01-19 3:38 ` Xinliang Liu
2016-01-19 16:03 ` Carlos Palminha
2016-01-19 16:03 ` Carlos Palminha
2016-01-19 16:52 ` Carlos Palminha
2016-01-19 16:52 ` Carlos Palminha
2016-01-20 1:24 ` Xinliang Liu
2016-01-20 1:24 ` Xinliang Liu
2016-01-21 18:09 ` Carlos Palminha
2016-01-21 18:09 ` Carlos Palminha
2016-01-21 18:30 ` Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return Carlos Palminha
2016-01-21 18:30 ` Carlos Palminha
2016-01-21 18:30 ` Carlos Palminha
2016-01-22 8:32 ` Daniel Stone
2016-01-22 8:32 ` Daniel Stone
2016-01-22 8:32 ` Daniel Stone
2016-01-28 14:20 ` Alexey Brodkin [this message]
2016-01-28 14:20 ` Alexey Brodkin
2016-01-28 14:20 ` Alexey Brodkin
2016-01-28 15:42 ` Rob Clark
2016-01-28 15:42 ` Rob Clark
2016-01-28 15:42 ` Rob Clark
2016-01-22 7:41 ` Whats missing in my new FB DRM driver... "No connectors reported connected with modes"? Daniel Vetter
2016-01-22 7:41 ` Daniel Vetter
2016-01-22 8:34 ` Daniel Stone
2016-01-22 8:34 ` Daniel Stone
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=1453990837.4304.15.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=tomi.valkeinen@ti.com \
--cc=xinliang.liu@linaro.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.