Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Inki Dae <inki.dae@samsung.com>
Cc: Tobias Jakobi <liquid.acid@gmx.net>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: drm/exynos: Add atomic modesetting support
Date: Tue, 12 May 2015 15:29:08 -0300	[thread overview]
Message-ID: <20150512182908.GB3327@joana> (raw)
In-Reply-To: <CAAQKjZMRG_a1FrTRD9dACSBz8w3zvrLYWSSM0-wUbaVePaPA2Q@mail.gmail.com>

2015-05-10 Inki Dae <inki.dae@samsung.com>:

> 2015-05-09 21:13 GMT+09:00 Tobias Jakobi <liquid.acid@gmx.net>:
> > Hello Inki,
> >
> >
> > Inki Dae wrote:
> >> Hi,
> >>
> >> 2015-05-09 6:51 GMT+09:00 Tobias Jakobi <liquid.acid@gmx.net>:
> >>> Hello,
> >>>
> >>> I've tested this on my Hardkernel Odroid-X2 (connected via HDMI to a
> >>> 1080p panel).
> >>>
> >>> Run the usual modetest tests (just primary plane, primary plane with
> >>> vsync, primary plane with overlay, primary plane with overlay and video
> >>> overlay, overlay partially outside of crtc area, etc.) and haven't
> >>> noticed any issues so far.
> >>
> >> As I mentioned several times, it works well in case that only one crtc
> >> driver is enabled. Could you check it again after you enable two or
> >> more crtc drivers such as FIMD and HDMI or FIMD, HDMI and VIDI
> >> together? For this, dts file for X2 should contain their device nodes
> >> and also should be configurated though menuconfig.
> > I've enabled VIDI and FIMD and confirmed that they should up properly in
> > modetest before applying the series.
> >
> > Booting with the atomic series works fine, but I get a segfault when
> > calling modetest. I've attached the kernel log below.
> 
> Below panic issue is same as one I faced with at previous patch seris,
> v3, which was invalid memory access - state->crtc is NULL whille
> modetest is being performed. It seems that the last patch of v4 didn't
> resolve this issue yet.

The weird thing is that it works quite fine on my exynos 5 hardware.
I'll take a look on what could be be happening to cause this kind of
crash.

	Gustavo

  reply	other threads:[~2015-05-12 18:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30 21:50 drm/exynos: Add atomic modesetting support Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 01/12] drm/exynos: atomic phase 1: use drm_plane_helper_update() Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 02/12] drm/exynos: atomic phase 1: use drm_plane_helper_disable() Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 03/12] drm/exynos: atomic phase 1: add .mode_set_nofb() callback Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 04/12] drm/exynos: atomic phase 2: wire up state reset(), duplicate() and destroy() Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 05/12] drm/exynos: atomic phase 2: keep track of framebuffer pointer Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 06/12] drm/exynos: atomic phase 3: atomic updates of planes Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 07/12] drm/exynos: atomic phase 3: use atomic .set_config helper Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 08/12] drm/exynos: atomic phase 3: convert page flips Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 09/12] drm/exynos: remove exported functions from exynos_drm_plane Gustavo Padovan
2015-05-08 23:36   ` Tobias Jakobi
2015-04-30 21:50 ` [PATCH v4 10/12] drm/exynos: don't disable unused functions at init Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 11/12] drm/exynos: atomic dpms support Gustavo Padovan
2015-04-30 21:50 ` [PATCH v4 12/12] drm/exynos: remove unnecessary calls to disable_plane() Gustavo Padovan
2015-05-06 21:45 ` drm/exynos: Add atomic modesetting support Gustavo Padovan
2015-05-07  2:45   ` Inki Dae
2015-05-08 21:45     ` Gustavo Padovan
2015-05-08 21:51 ` Tobias Jakobi
2015-05-09 10:23   ` Inki Dae
2015-05-09 12:13     ` Tobias Jakobi
2015-05-09 12:20       ` Tobias Jakobi
2015-05-09 12:30         ` Tobias Jakobi
2015-05-10 13:54       ` Inki Dae
2015-05-12 18:29         ` Gustavo Padovan [this message]
2015-05-14 18:41           ` Gustavo Padovan
  -- strict thread matches above, loose matches on Subject: below --
2015-05-15 10:16 Tobias Jakobi
2015-05-15 11:44 Tobias Jakobi
2015-05-18 19:51 ` Gustavo Padovan
2015-05-18 20:35   ` Daniel Stone
2015-05-18 21:02     ` Gustavo Padovan
2015-05-19 13:53       ` Tobias Jakobi
2015-05-19 14:06         ` Daniel Stone
2015-05-19 14:52           ` Tobias Jakobi
2015-05-19 17:27           ` Tobias Jakobi
2015-05-19 18:43             ` Gustavo Padovan
2015-05-19 18:54               ` 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=20150512182908.GB3327@joana \
    --to=gustavo@padovan.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=liquid.acid@gmx.net \
    /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