[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160428174215.GS3217@sirena.org.uk>
Date: Thu, 28 Apr 2016 18:42:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Octavian Purdila <octavian.purdila@...el.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <lenb@...nel.org>,
Matt Fleming <matt@...eblueprint.co.uk>,
Wolfram Sang <wsa@...-dreams.de>,
Joel Becker <jlbec@...lplan.org>, linux-acpi@...r.kernel.org,
linux-efi@...r.kernel.org, linux-i2c@...r.kernel.org,
linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
irina.tirdea@...el.com
Subject: Re: [RFC PATCH v2 06/10] spi: add support for ACPI reconfigure
notifications
On Wed, Apr 20, 2016 at 01:39:04AM +0300, Octavian Purdila wrote:
> + switch (value) {
> + case ACPI_RECONFIG_DEVICE_ADD:
> + master = acpi_spi_find_master_by_adev(adev->parent);
> + if (!master)
> + break;
> +
> + acpi_register_spi_device(master, adev);
> + put_device(&master->dev);
> + break;
> + case ACPI_RECONFIG_DEVICE_REMOVE:
> + spi = acpi_spi_find_device_by_adev(adev);
> + if (!spi)
> + break;
There's more code here now than I remember but this all looks *really*
close to the DT code except for the OF_POPULATED flag that we set when
things are instantiated in DT. The duplication seems bad but the fact
that we're missing the flag worries me... do we have guarantees that
ACPI won't double register?
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists