From: Tony Lindgren <tony@atomide.com>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: "Peter Ujfalusi" <peter.ujfalusi@ti.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: EDMA oftree entry for AM335x
Date: Tue, 9 Jun 2015 22:10:38 -0700 [thread overview]
Message-ID: <20150610051037.GA2740@atomide.com> (raw)
In-Reply-To: <20150608105957.GT26523@pengutronix.de>
* Robert Schwebel <r.schwebel@pengutronix.de> [150608 04:01]:
> On Wed, May 06, 2015 at 07:39:52AM -0700, Tony Lindgren wrote:
> >
> > That may never happen considering that davinci is using it too.. It's
> > best to not count on that happening anytime soon at least.
>
> So my current understanding is that we have the situation that the
> kernel warns about the oftree being wrong, but isn't able to handle an
> oftree that would be right.
>
> Shouldn't the warning being added when the kernel driver supports that
> new mechanism?
This particular driver is broken and it needs to be fixed properly.
> I had a warning free mainline kernel without patches on my customer
> hardware before, so this smells a bit like a regression ... :-/
Yes sorry I'm not patching away the warning as it does not fix the
driver. Peter, I assume you are busy fixing it?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: EDMA oftree entry for AM335x
Date: Tue, 9 Jun 2015 22:10:38 -0700 [thread overview]
Message-ID: <20150610051037.GA2740@atomide.com> (raw)
In-Reply-To: <20150608105957.GT26523@pengutronix.de>
* Robert Schwebel <r.schwebel@pengutronix.de> [150608 04:01]:
> On Wed, May 06, 2015 at 07:39:52AM -0700, Tony Lindgren wrote:
> >
> > That may never happen considering that davinci is using it too.. It's
> > best to not count on that happening anytime soon at least.
>
> So my current understanding is that we have the situation that the
> kernel warns about the oftree being wrong, but isn't able to handle an
> oftree that would be right.
>
> Shouldn't the warning being added when the kernel driver supports that
> new mechanism?
This particular driver is broken and it needs to be fixed properly.
> I had a warning free mainline kernel without patches on my customer
> hardware before, so this smells a bit like a regression ... :-/
Yes sorry I'm not patching away the warning as it does not fix the
driver. Peter, I assume you are busy fixing it?
Regards,
Tony
next prev parent reply other threads:[~2015-06-10 5:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 6:43 EDMA oftree entry for AM335x Robert Schwebel
2015-05-04 6:43 ` Robert Schwebel
2015-05-04 14:11 ` Tony Lindgren
2015-05-04 14:11 ` Tony Lindgren
2015-05-04 21:11 ` Robert Schwebel
2015-05-04 21:11 ` Robert Schwebel
2015-05-04 21:24 ` Tony Lindgren
2015-05-04 21:24 ` Tony Lindgren
2015-05-04 21:33 ` Robert Schwebel
2015-05-04 21:33 ` Robert Schwebel
2015-05-04 21:42 ` Tony Lindgren
2015-05-04 21:42 ` Tony Lindgren
2015-05-05 13:53 ` Peter Ujfalusi
2015-05-05 13:53 ` Peter Ujfalusi
2015-05-05 14:58 ` Tony Lindgren
2015-05-05 14:58 ` Tony Lindgren
2015-05-06 11:22 ` Peter Ujfalusi
2015-05-06 11:22 ` Peter Ujfalusi
2015-05-06 14:39 ` Tony Lindgren
2015-05-06 14:39 ` Tony Lindgren
2015-06-08 10:59 ` Robert Schwebel
2015-06-08 10:59 ` Robert Schwebel
2015-06-10 5:10 ` Tony Lindgren [this message]
2015-06-10 5:10 ` Tony Lindgren
2015-06-10 11:13 ` Peter Ujfalusi
2015-06-10 11:13 ` Peter Ujfalusi
2015-06-11 14:13 ` Tony Lindgren
2015-06-11 14:13 ` Tony Lindgren
2015-06-11 14:53 ` Peter Ujfalusi
2015-06-11 14:53 ` Peter Ujfalusi
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=20150610051037.GA2740@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=r.schwebel@pengutronix.de \
/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.