[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150607140138.026C4C412C8@trevor.secretlab.ca>
Date: Sun, 07 Jun 2015 15:01:37 +0100
From: Grant Likely <grant.likely@...aro.org>
To: Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>,
Rob Herring <robherring2@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Vivek Goyal <vgoyal@...hat.com>,
Jakub Sitnicki <jsitnicki@...il.com>,
Mike Travis <travis@....com>,
Jiang Liu <jiang.liu@...ux.intel.com>,
Thierry Reding <treding@...dia.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Tejun Heo <tj@...nel.org>, Cliff Wickman <cpw@....com>
Subject: Re: [PATCH 2/2] of/platform: Mark all device tree resources as
SHARED
On Fri, 5 Jun 2015 18:51:36 +0200
, Ricardo Ribalda Delgado <ricardo.ribalda@...il.com>
wrote:
> Hello Rob,
>
> Thanks for your feedback!
>
> On Fri, Jun 5, 2015 at 6:45 PM, Rob Herring <robherring2@...il.com> wrote:
> > On Fri, Jun 5, 2015 at 5:51 AM, Ricardo Ribalda Delgado
> > <ricardo.ribalda@...il.com> wrote:
> >> Some device tree platform do not define their resources properly. i.e.
> >> overlapping or repeated resources.
> >>
> >> This patch mark all device tree resources as shareable.
> >>
> >> In the future this should only be set for the platforms that have
> >> problems.
> >
> > I don't think we want to do this globally. This should be very rare
> > and we want to discourage any new cases.
>
> I just wanted to mimic the original behaviour. Unfortunately I have no
> idea of what platform is broken. Grant needs to help us here :)
I know of powerpc platforms that split the ethernet and mdio controllers
into separate nodes, even though they share a register block. Those ones
are broken (ie. mpc5200). I know there are ARM platforms that exhibited
the same behaviour, but I can't remember specifics at the moment.
> What do you think about the new flag? Does it make any sense for you?
I think I have another solution to the whole problem. IIUC, the problem
is the kernel crashes on unregistering resources. I've got a patch that
doesn't try to unregister resources that weren't registered in the first
place. It doesn't fix the problem of DT not registering the resources in
the first place, but it makes the unregister path safe.
I'll cc: you on the patch series.
g.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists