dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "m.szyprowski@samsung.com" <m.szyprowski@samsung.com>
Cc: "robh@kernel.org" <robh@kernel.org>,
	"s.nawrocki@samsung.com" <s.nawrocki@samsung.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"Liviu.Dudau@arm.com" <Liviu.Dudau@arm.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"linux-snps-arc@lists.infradead.org"
	<linux-snps-arc@lists.infradead.org>
Subject: Re: of_reserved_mem_device_init_by_idx() returns -EINVAL if "memory-region" is missing
Date: Fri, 17 Jun 2016 06:47:47 +0000	[thread overview]
Message-ID: <1466146013.2948.1.camel@synopsys.com> (raw)
In-Reply-To: <b26dcbc6-758a-a08f-b258-945548aab3dc@samsung.com>

Hi Marek,

On Fri, 2016-06-17 at 07:28 +0200, Marek Szyprowski wrote:
> Hi Alexey
> 
> 
> On 2016-06-16 18:47, Alexey Brodkin wrote:
> > 
> > Hi Marek,
> > 
> > We used to use of_reserved_mem_device_init() in such a context in GPU drivers:
> > -------------------->8-------------------
> > 	/* Get the optional framebuffer memory resource */
> > 	ret = of_reserved_mem_device_init(drm->dev);
> > 	if (ret && ret != -ENODEV)
> > 		return ret;
> > -------------------->8-------------------
> > 
> > The point is we may have a dedicated reserved memory area or may not have (depends on a particular .dts).
> > Our expectation is if reserved memory area is missing then of_reserved_mem_device_init()
> > just returns -ENODEV and it used to work like this.
> > 
> > Now with your commit 59ce4039727e "of: reserved_mem: add support for using more than one region for given device"
> > behavior is different. of_reserved_mem_device_init_by_idx() has this:
> > -------------------->8-------------------
> > 	target = of_parse_phandle(np, "memory-region", idx);
> > 	if (!target)
> > 		return -EINVAL;
> > -------------------->8-------------------
> > 
> > So I'm wondering which part should be fixed:
> >   1) of_reserved_mem itself or
> >   2) users of of_reserved_mem_device_init()
> > 
> > Any thoughts?
> 
> This was my fault. The fix is already queued to linux-next, see commit
> 9f5a802b1d51dc80a27d828a5f7dcc8ec4a72f03 ("[media] of: reserved_mem: restore
> old behavior when no region is defined"),
> http://www.spinics.net/lists/linux-media/msg100972.html
> 

Indeed with mentioned fix GPU driver now works again!
Sorry for the noise and thank you for fixing it that fast.

Regards,
Alexey
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc

      reply	other threads:[~2016-06-17  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16 16:47 of_reserved_mem_device_init_by_idx() returns -EINVAL if "memory-region" is missing Alexey Brodkin
2016-06-17  5:28 ` Marek Szyprowski
2016-06-17  6:47   ` Alexey Brodkin [this message]

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=1466146013.2948.1.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-snps-arc@lists.infradead.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robh@kernel.org \
    --cc=s.nawrocki@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox