linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <mbrugger@suse.com>
To: Brijesh Singh <brijesh.singh@amd.com>,
	Arnd Bergmann <arnd@arndb.de>, Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, hdegoede@redhat.com,
	linux-ide@vger.kernel.org, Graeme Gregory <graeme@xora.org.uk>
Subject: Re: [PATCH v2] ata: add AMD Seattle platform driver
Date: Thu, 14 Apr 2016 11:08:36 +0200	[thread overview]
Message-ID: <570F5E14.9020403@suse.com> (raw)
In-Reply-To: <56EC4AB8.7040901@amd.com>

Hi Brijesh,

On 18/03/16 19:36, Brijesh Singh wrote:
> Hi Tejun,
>
> On 03/17/2016 12:36 PM, Arnd Bergmann wrote:
>> On Wednesday 16 March 2016 14:07:13 Tejun Heo wrote:
>>> Hello, Arnd.
>>>
>>> On Mon, Feb 01, 2016 at 09:14:17PM +0100, Arnd Bergmann wrote:
>>>>> I am not debating on your AML call recommendation, it sounds like
>>>>> a good idea however BIOS is already released hence its bit late to
>>>>> add AML methods for this. I am seeking guidance on what can be
>>>>> done in the given situation. I thought platform driver is one
>>>>> option to get this feature enabled in kernel.
>>>
>>>> This is where we really need the ACPI maintainers to explain the
>>>> general policy for dealing with firmware updates.
>>>>
>>>> I would assume that adding the feature in a later firmware version
>>>> is a compatible change, and the feature is non-essential (the
>>>> device will work fine with the generic SATA driver, except
>>>> the LEDs don't blink), so it's not a big deal, it's just what
>>>> you get for having the firmware shipped before the driver is
>>>> reviewed (don't do that).
>>>
>>> So, if it were x86, I'd commit the custom driver without thinking too
>>> much as ata drivers have always been working around bios issues (there
>>> often wasn't any other recourse).  If the hardware is already out
>>> there and it's not too easy to roll out bios updates, from libata
>>> side, I'm okay with having a custom driver to work around that.  What
>>> do you think?
>>
>>
>> It's your call in the end. My main objection is to the fact that
>> I have suggested a clean implementation for the normal DT based
>> path that also fixes existing platforms that used to work in the
>> past and were broken by the (long-ago) move from drivers/ide to
>> drivers/ata, Brijesh has not implemented that but has instead
>> continued pushing the hack for the ACPI mode that is still
>> experimental on ARM64.
>>
>
> I am helping a customer who want EM support in a distro (using ACPI mode). Since its difficult to update
> the bios hence can I request to pull this driver. The driver solves the ACPI usecases.
>
> As per DT is concerned, will look into driver/ide and led framework but since I am not very familiar with
> driver/ide and led framework hence it will take sometime to design and implement the DT cases.
>

Did you made any progress on the DT part?

Regards,
Matthias

  parent reply	other threads:[~2016-04-14  9:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 16:31 [PATCH v2] ata: add AMD Seattle platform driver Brijesh Singh
2016-01-20 21:24 ` Brijesh Singh
2016-01-25 20:43 ` Tejun Heo
2016-01-26  9:36   ` Hans de Goede
2016-03-16 20:12     ` Brijesh Singh
2016-01-26 12:17   ` Arnd Bergmann
2016-01-26 16:56     ` Brijesh Singh
2016-01-29 21:22       ` Arnd Bergmann
2016-01-29 21:31         ` One Thousand Gnomes
2016-02-01 18:56         ` Brijesh Singh
2016-02-01 20:14           ` Arnd Bergmann
2016-02-01 22:15             ` Brijesh Singh
2016-02-02 14:08               ` Arnd Bergmann
2016-02-02 18:37                 ` Brijesh Singh
2016-02-05 14:50                   ` Arnd Bergmann
2016-02-05 17:23                     ` Brijesh Singh
2016-02-08 18:12                       ` Brijesh Singh
2016-03-16 21:07             ` Tejun Heo
2016-03-17 17:36               ` Arnd Bergmann
2016-03-18 18:36                 ` Brijesh Singh
2016-03-18 20:19                   ` Tejun Heo
2016-04-14  9:08                   ` Matthias Brugger [this message]
2016-04-14 22:14                     ` Brijesh Singh
2016-04-13 19:15 ` Tejun Heo

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=570F5E14.9020403@suse.com \
    --to=mbrugger@suse.com \
    --cc=arnd@arndb.de \
    --cc=brijesh.singh@amd.com \
    --cc=graeme@xora.org.uk \
    --cc=hdegoede@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).