[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5693DE9A.9070101@amd.com>
Date: Mon, 11 Jan 2016 10:55:54 -0600
From: Brijesh Singh <brijesh.singh@....com>
To: Mark Langsdorf <mlangsdo@...hat.com>, Arnd Bergmann <arnd@...db.de>
CC: <brijesh.singh@....com>, <linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <mark.rutland@....com>,
<devicetree@...r.kernel.org>, <pawel.moll@....com>,
<ijc+devicetree@...lion.org.uk>, <linux-ide@...r.kernel.org>,
<robh+dt@...nel.org>, <galak@...eaurora.org>, <tj@...nel.org>
Subject: Re: [PATCH] ata: add AMD Seattle platform driver
Hi,
On 01/11/2016 09:33 AM, Mark Langsdorf wrote:
> On 01/08/2016 04:21 PM, Brijesh Singh wrote:
>>
>> libata-*.c implements the "Enclosure management" style led messages but also has hooks
>> to register a custom led control callback. Since Seattle platform does not support
>> the "Enclosure management" registers hence ata_port_info we are setting a ATA_FLAG_EM | ATA_FLAG_SW_ACIVITY
>> to indicate that we can still handle the led messages by our registered callback. I see
>> that sata_highbank driver is doing something similar.
>
> The sata_highbank driver is doing it wrong and shouldn't have been
> accepted in its current condition. Enclosure management really should
> be a separate device. Please don't use it as an example.
>
Okay. Thanks for letting me know.
Should I consider extending the generic driver to handle this Seattle platform specific feature or go with a new
platform driver approach (i.e the one I am doing right now) ?
-Brijesh
Powered by blists - more mailing lists