From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Tejun Heo <tj@kernel.org>, Jason Cooper <jason@lakedaemon.net>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Revert "ata: sata_mv: Convert to devm_ioremap_resource()"
Date: Thu, 25 May 2017 15:53:40 +0300 [thread overview]
Message-ID: <1495716820.6967.111.camel@linux.intel.com> (raw)
In-Reply-To: <20170524142956.GE26577@lunn.ch>
On Wed, 2017-05-24 at 16:29 +0200, Andrew Lunn wrote:
> On Wed, May 24, 2017 at 05:00:04PM +0300, Andy Shevchenko wrote:
> > On Wed, 2017-05-24 at 15:41 +0200, Andrew Lunn wrote:
> > > > I'm wondering where exactly first resource acquiring is
> > > > happening.
> > >
> > > drivers/phy/phy-mvebu-sata.c
> > >
> >
> > In which tree? I have nothing like this in linux-next.
>
> git log drivers/phy/phy-mvebu-sata.c
>
> It has been there since Tue Dec 17 21:21:50 2013.
>
> > I'm on the side that revert just hides the real issue back.
>
> What issue? You are allowed to have overlapping memory resources.
Exactly, and then the question why did you do a revert?
AFAIU the problem is that platform core tries to reserve the resource
and you can't do it twice for overlapping region (see insert_resource()
call implementation).
Since it's allowed and we have more devices which requires that
(basically that ones that have phy embedded in common address space) we
might reconsider the policy used in platform core.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2017-05-25 12:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 23:39 [PATCH] Revert "ata: sata_mv: Convert to devm_ioremap_resource()" Andrew Lunn
2017-05-24 13:01 ` Gregory CLEMENT
2017-05-24 13:12 ` Andrew Lunn
2017-05-24 13:36 ` Andy Shevchenko
2017-05-24 13:41 ` Andrew Lunn
2017-05-24 14:00 ` Andy Shevchenko
2017-05-24 14:11 ` Gregory CLEMENT
2017-05-24 14:29 ` Andrew Lunn
2017-05-25 12:53 ` Andy Shevchenko [this message]
2017-05-25 13:26 ` Andrew Lunn
2017-05-25 13:34 ` Andy Shevchenko
2017-05-24 15:07 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2017-05-30 13:52 Linus Walleij
2017-05-30 13:55 ` Andy Shevchenko
2017-05-30 23:53 ` Linus Walleij
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=1495716820.6967.111.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andrew@lunn.ch \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox