linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dwmw2@infradead.org (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Convert smsc911x to use ACPI as well as DT
Date: Sat, 26 Sep 2015 16:20:51 +0100	[thread overview]
Message-ID: <1443280851.4674.63.camel@infradead.org> (raw)
In-Reply-To: <20150925152848.GQ13823@e104818-lin.cambridge.arm.com>

On Fri, 2015-09-25 at 16:28 +0100, Catalin Marinas wrote:
> 
> This only works as long as they target an existing driver with prior DT
> support (usually with reviewed bindings). If they have a new driver and
> only ACPI in mind, I'm pretty sure we'll end up with new insane things.
> That's why we need some form of _DSD properties review and "compatible"
> is one such property.

Sure, that makes a lot of sense.

My main concern is that we don't end up with gratuitously *different*
property sets for DT vs. ACPI. That way we end up with either two
separate drivers, or abstracting the core of the driver out and having
two bindings for it (much as we do for PCI vs. platform/etc for some
devices already). We don't want that pain where we can avoid it. And we
don't want people to *have* to hack the kernel driver to migrate to
ACPI, if we can avoid it.


Sometimes it might be worth being different ? if the DT binding is
utterly crap, and deserves to be thrown away. In that case, by all
means invent a new binding. But if we're going to accept the pain of
having multiple bindings, why not make the *new* one work via DT too
anyway.

I'd be happy to see the existing DT bindings put through the nascent
_DSD review process ? such as it is ? and into the database. One at a
time on a case-by-case basis as they get used, perhaps.

-- 
dwmw2

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5691 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150926/fe7b2387/attachment.bin>

  parent reply	other threads:[~2015-09-26 15:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 22:06 [PATCH 0/2] Enable smsc911x for use with ACPI Jeremy Linton
2015-08-12 22:06 ` [PATCH 1/2] Add a matching set of device_ functions for determining mac/phy Jeremy Linton
2015-08-12 22:13   ` Florian Fainelli
2015-08-14 15:55     ` Jeremy Linton
2015-08-13 11:57   ` Robin Murphy
2015-08-13 14:24     ` Jeremy Linton
2015-08-12 22:06 ` [PATCH 2/2] Convert smsc911x to use ACPI as well as DT Jeremy Linton
2015-08-13  8:27   ` Graeme Gregory
2015-08-13  9:01     ` Lorenzo Pieralisi
2015-08-13  9:38       ` Graeme Gregory
2015-08-13 10:30         ` Lorenzo Pieralisi
2015-09-09 16:10   ` Marc Zyngier
2015-09-23 17:22     ` Jeremy Linton
2015-09-23 17:46       ` Marc Zyngier
2015-09-23 17:57       ` Sudeep Holla
2015-09-24  9:20         ` Catalin Marinas
2015-11-02 15:48     ` Jeremy Linton
2015-09-23 18:41   ` David Woodhouse
2015-09-23 20:51     ` Rafael J. Wysocki
2015-09-23 21:03       ` David Woodhouse
2015-09-23 23:56         ` Hanjun Guo
2015-09-24  8:16           ` David Woodhouse
2015-09-24 10:31             ` Catalin Marinas
2015-09-24 11:52               ` David Woodhouse
2015-09-24 14:01                 ` Lorenzo Pieralisi
2015-09-24 14:31                   ` David Woodhouse
2015-09-24 15:15                 ` Catalin Marinas
2015-09-24 18:10                   ` David Woodhouse
2015-09-25 15:28                     ` Catalin Marinas
2015-09-26  2:16                       ` Rafael J. Wysocki
2015-09-26 15:20                       ` David Woodhouse [this message]
2015-10-01  2:23                       ` Al Stone
2015-10-06  0:20                         ` Charles Garcia-Tobin
2015-10-06 11:08                           ` David Woodhouse
2015-10-08  0:11                             ` Rafael J. Wysocki
2015-08-14  0:00 ` [PATCH 0/2] Enable smsc911x for use with ACPI David Miller

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=1443280851.4674.63.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.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).