From: Wolfram Sang <wsa@the-dreams.de>
To: Grant Likely <grant.likely@linaro.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Subject: Re: [PATCH 2/2] drivercore: Fix unregistration path of platform devices
Date: Mon, 15 Jun 2015 18:46:30 +0200 [thread overview]
Message-ID: <20150615164630.GC1583@katana> (raw)
In-Reply-To: <1433686811-12303-3-git-send-email-grant.likely@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]
On Sun, Jun 07, 2015 at 03:20:11PM +0100, Grant Likely wrote:
> The unregister path of platform_device is broken. On registration, it
> will register all resources with either a parent already set, or
> type==IORESOURCE_{IO,MEM}. However, on unregister it will release
> everything with type==IORESOURCE_{IO,MEM}, but ignore the others. There
> are also cases where resources don't get registered in the first place,
> like with devices created by of_platform_populate()*.
>
> Fix the unregister path to be symmetrical with the register path by
> checking the parent pointer instead of the type field to decide which
> resources to unregister. This is safe because the upshot of the
> registration path algorithm is that registered resources have a parent
> pointer, and non-registered resources do not.
>
> * It can be argued that of_platform_populate() should be registering
> it's resources, and they argument has some merit. However, there are
> quite a few platforms that end up broken if we try to do that due to
> overlapping resources in the device tree. Until that is fixed, we need
> to solve the immediate problem.
>
> Cc: Pantelis Antoniou <pantelis.antoniou@konsulko.com>
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
> Signed-off-by: Grant Likely <grant.likely@linaro.org>
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-15 16:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 14:20 [PATCH 0/2] Fix oops in platform_device resource unregister Grant Likely
2015-06-07 14:20 ` [PATCH 1/2] of/unittest: Show broken behaviour in the platform bus Grant Likely
2015-06-08 20:16 ` Rob Herring
2015-06-09 11:05 ` Grant Likely
2015-06-15 16:45 ` Wolfram Sang
2015-06-07 14:20 ` [PATCH 2/2] drivercore: Fix unregistration path of platform devices Grant Likely
2015-06-07 18:13 ` Ricardo Ribalda Delgado
2015-06-08 8:14 ` Pantelis Antoniou
2015-06-08 8:42 ` Ricardo Ribalda Delgado
2015-06-08 18:47 ` Grant Likely
2015-06-08 20:09 ` Ricardo Ribalda Delgado
2015-06-08 20:47 ` Ricardo Ribalda Delgado
2015-06-09 11:00 ` Grant Likely
2015-06-10 0:22 ` Kevin Hilman
2015-06-10 7:11 ` Ricardo Ribalda Delgado
2015-06-10 14:03 ` Rob Herring
2015-06-16 7:58 ` Tony Lindgren
2015-06-10 14:38 ` Kevin Hilman
2015-06-10 14:46 ` Ricardo Ribalda Delgado
2015-06-10 15:34 ` Greg Kroah-Hartman
2015-06-10 15:40 ` Greg Kroah-Hartman
2015-06-10 17:11 ` Grant Likely
2015-06-10 17:12 ` Pantelis Antoniou
2015-06-10 23:38 ` Wolfram Sang
2015-06-12 14:00 ` Ricardo Ribalda Delgado
2015-06-15 16:46 ` Wolfram Sang [this message]
2015-06-23 17:12 ` Ricardo Ribalda Delgado
2015-07-16 20:33 ` Ricardo Ribalda Delgado
2015-08-22 12:57 ` Ricardo Ribalda Delgado
2015-08-23 21:52 ` Rob Herring
2015-08-23 21:58 ` Ricardo Ribalda Delgado
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=20150615164630.GC1583@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=ricardo.ribalda@gmail.com \
--cc=robh@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