From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Meng Yi <meng.yi@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Mark Brown <broonie@kernel.org>,
"airlied@redhat.com" <airlied@redhat.com>
Subject: Re: fsl-dcu not works on latest "drm-next"
Date: Thu, 26 May 2016 11:11:27 +0200 [thread overview]
Message-ID: <9218011.3pJWMXVBWr@ws-stein> (raw)
In-Reply-To: <HE1PR04MB10512AE47A7F3867160B5325EC410@HE1PR04MB1051.eurprd04.prod.outlook.com>
On Thursday 26 May 2016 08:18:30, Meng Yi wrote:
> Hi Alexander,
>
> > From your backtrace I guess wait_event_timeout is called in some atomic
> > context (might_sleep(); is called inside wait_event_timeout). This has
> > nothing to do with regmap.
>
> Here is my view of point:
> Since IRQ setup codes using regmap, and which is not setup properly, so
> wait_event_timeout.
> > The inital problem came up with 922a9f936e40001f9b921379aab90047d5990923
> > ("regmap: mmio: Convert to regmap_bus and fix accessor usage"). The
> > commits 9f9f8b863ad130ec0c25f378bdbad64ba71291de,
> > 4f7d6dd4df8b388e2056c89b528254cdd79dea2a and
> > 0dbdb76c0ca8e7caf27c9a210f64c4359e2974a4 tried to fix that. With those I
> > could successfully probe DCU.
>
> Thanks for your information.
> DCU was able to be probed without those patches, and DCU still not works
> with those patches.
Yes, sure. DCU was probed fine before
922a9f936e40001f9b921379aab90047d5990923. But this introduced a regression for
DCU and also DSPI on LS1021A which got fixed by the other 3 named commits.
I didn't try to use DCU for a while, maybe there is another regression.
Please try reverting 2ed94f6fde066fb37bc3553b786edb805561699e
If that helps the device tree probing does not work in regmap_get_val_endian
Best regards,
Alexander
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Meng Yi <meng.yi@nxp.com>
Cc: Stefan Agner <stefan@agner.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
"airlied@redhat.com" <airlied@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: fsl-dcu not works on latest "drm-next"
Date: Thu, 26 May 2016 11:11:27 +0200 [thread overview]
Message-ID: <9218011.3pJWMXVBWr@ws-stein> (raw)
In-Reply-To: <HE1PR04MB10512AE47A7F3867160B5325EC410@HE1PR04MB1051.eurprd04.prod.outlook.com>
On Thursday 26 May 2016 08:18:30, Meng Yi wrote:
> Hi Alexander,
>
> > From your backtrace I guess wait_event_timeout is called in some atomic
> > context (might_sleep(); is called inside wait_event_timeout). This has
> > nothing to do with regmap.
>
> Here is my view of point:
> Since IRQ setup codes using regmap, and which is not setup properly, so
> wait_event_timeout.
> > The inital problem came up with 922a9f936e40001f9b921379aab90047d5990923
> > ("regmap: mmio: Convert to regmap_bus and fix accessor usage"). The
> > commits 9f9f8b863ad130ec0c25f378bdbad64ba71291de,
> > 4f7d6dd4df8b388e2056c89b528254cdd79dea2a and
> > 0dbdb76c0ca8e7caf27c9a210f64c4359e2974a4 tried to fix that. With those I
> > could successfully probe DCU.
>
> Thanks for your information.
> DCU was able to be probed without those patches, and DCU still not works
> with those patches.
Yes, sure. DCU was probed fine before
922a9f936e40001f9b921379aab90047d5990923. But this introduced a regression for
DCU and also DSPI on LS1021A which got fixed by the other 3 named commits.
I didn't try to use DCU for a while, maybe there is another regression.
Please try reverting 2ed94f6fde066fb37bc3553b786edb805561699e
If that helps the device tree probing does not work in regmap_get_val_endian
Best regards,
Alexander
next prev parent reply other threads:[~2016-05-26 9:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 9:26 fsl-dcu not works on latest "drm-next" Meng Yi
2016-05-03 16:08 ` Stefan Agner
2016-05-04 3:40 ` Meng Yi
2016-05-25 2:14 ` Meng Yi
2016-05-25 6:20 ` Stefan Agner
2016-05-25 6:20 ` Stefan Agner
2016-05-25 8:32 ` Alexander Stein
2016-05-25 8:58 ` Meng Yi
2016-05-25 9:57 ` Alexander Stein
2016-05-25 10:25 ` Meng Yi
2016-05-25 12:16 ` Alexander Stein
2016-05-26 8:18 ` Meng Yi
2016-05-26 9:11 ` Alexander Stein [this message]
2016-05-26 9:11 ` Alexander Stein
2016-05-25 9:18 ` Mark Brown
2016-05-25 9:18 ` Mark Brown
2016-05-25 9:59 ` Meng Yi
2016-05-25 10:41 ` Mark Brown
2016-05-25 10:41 ` Mark Brown
2016-05-26 8:23 ` Meng Yi
2016-05-26 9:11 ` Alexander Stein
2016-05-27 5:54 ` Stefan Agner
2016-05-27 5:54 ` Stefan Agner
2016-05-27 12:20 ` Mark Brown
2016-05-27 12:20 ` Mark Brown
2016-05-27 17:36 ` Stefan Agner
2016-05-27 17:36 ` Stefan Agner
2016-05-27 19:50 ` Mark Brown
2016-06-03 22:52 ` Stefan Agner
2016-06-03 22:52 ` Stefan Agner
2016-06-07 2:16 ` Meng Yi
2016-06-07 2:46 ` Stefan Agner
2016-06-07 2:46 ` Stefan Agner
2016-06-07 3:47 ` Meng Yi
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=9218011.3pJWMXVBWr@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=airlied@redhat.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=meng.yi@nxp.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 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.