All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Ben Gardner <gardner.ben@gmail.com>
Cc: Dustin Byford <dustin@cumulusnetworks.com>, linux-acpi@vger.kernel.org
Subject: Re: ACPI: Can I use I2cSerialBus with a PCI I2C controller?
Date: Mon, 2 Nov 2015 12:25:02 +0200	[thread overview]
Message-ID: <20151102102502.GC1509@lahna.fi.intel.com> (raw)
In-Reply-To: <CAE7DoPbPuHTEZGvRTPrUXVCWLHwWPow9_1W15kHLTgXWQtwXUw@mail.gmail.com>

On Fri, Oct 30, 2015 at 11:51:01AM -0500, Ben Gardner wrote:
> It looks like you are supposed to have the first compatible entry be
> the exact manufacturer,model.
> http://devicetree.org/Device_Tree_Usage#Understanding_the_compatible_Property
> 
> I am considering using a generic compatible entry ("linux,at24") to
> match the Linux at24 driver.
> In my case, I'm using a M24C02 from ST, so the compatible line would be:
> 
>   Package () {"compatible", Package () {"st,m24c02", "linux,at24"}},
>   Package () {"size", 256},
>   Package () {"pagesize", 16},
> 
> The "linux,at24" would require the other properties (size and
> pagesize) to be present.
> I've seen something similar done with a few other devices.

Using "linux,foo" is not a good idea and I'm pretty sure DT maintainers
will not take such patches. The compatible (and other properties as
well) should describe hardware not software.

> > Alternatively we may use the same _HID "INT3499" as Andy is doing in his
> > series with the below properties.
> 
> The only issue with reusing INT3499 is that it is configured to be a
> 24C08 in the at24 driver.
> Reusing the 24C08 HID for a 24C02 or other chip might be a bit confusing.

It could default to 24c08 but if it has properties the driver should use
those to determine size etc.

      reply	other threads:[~2015-11-02 10:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 19:47 ACPI: Can I use I2cSerialBus with a PCI I2C controller? Ben Gardner
2015-10-21  8:50 ` Mika Westerberg
2015-10-21 23:14   ` Ben Gardner
2015-10-22  8:01     ` Mika Westerberg
2015-10-22 16:19       ` Ben Gardner
2015-10-22 17:17         ` Ben Gardner
2015-10-23  8:20           ` Mika Westerberg
2015-10-23  9:43             ` Mika Westerberg
2015-10-23 17:24             ` Ben Gardner
2015-10-26 19:56               ` Ben Gardner
2015-10-27 10:49                 ` Mika Westerberg
2015-10-27 21:11             ` Dustin Byford
2015-10-28  9:01               ` Mika Westerberg
2015-10-30 16:51                 ` Ben Gardner
2015-11-02 10:25                   ` Mika Westerberg [this message]

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=20151102102502.GC1509@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=dustin@cumulusnetworks.com \
    --cc=gardner.ben@gmail.com \
    --cc=linux-acpi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.