[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160216163143.GD19428@n2100.arm.linux.org.uk>
Date: Tue, 16 Feb 2016 16:31:43 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Marek Szyprowski <m.szyprowski@...sung.com>
Cc: Ulf Hansson <ulf.hansson@...aro.org>,
linux-samsung-soc@...r.kernel.org,
Tomeu Vizoso <tomeu.vizoso@...labora.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
linux-kernel@...r.kernel.org, Kukjin Kim <kgene@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 RESEND 4/5] ARM: amba: Move reading of periphid to
amba_match()
On Mon, Feb 15, 2016 at 05:52:50PM +0000, Russell King - ARM Linux wrote:
> On Wed, Feb 10, 2016 at 11:47:29AM +0100, Marek Szyprowski wrote:
> > From: Tomeu Vizoso <tomeu.vizoso@...labora.com>
> >
> > Reading the periphid when the Primecell device is registered means that
> > the apb pclk must be available by then or the device won't be registered
> > at all.
> >
> > By reading the periphid in amba_match() we can return -EPROBE_DEFER if
> > the apb pclk isn't there yet and the device will be retried later.
>
> I've just realised, we can't do this. We need to read the peripheral
> ID at registration time, because that's published to userspace via
> (a) a sysfs attribute, and (b) as part of the uevent, which will be
> used by udev to locate the driver module.
>
> So, this will have the side effect of breaking systems which have
> AMBA primecell devices configured as modules.
>
> Sorry, I can't apply this. We can't regress existing platforms for
> the sake of introducing new platforms to this code.
I just re-applied the patch set to the amba branch, and then dropped
the last two patches because of this issue. Please ignore the "applied"
notification for the last two patches from the patch system.
--
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
Powered by blists - more mailing lists