public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-i2c@vger.kernel.org
Subject: Re: [PATCH 4/4] eeprom: at24: Add OF device ID table
Date: Wed, 15 Mar 2017 08:58:35 +0100	[thread overview]
Message-ID: <20170315075835.GA1438@katana> (raw)
In-Reply-To: <8e233f15-4f91-b495-5270-5a7f982b31be@osg.samsung.com>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]


> So there isn't an agreement if is better to just rely in the current behavior
> (and have a superfluous I2C device ID table) or fix the I2C core (and need a
> OF device ID table).

For at24, the i2c_device_id table is not superfluous! It is used outside
the DT world as well.

> Indeed, but these all are compatible strings used by DTS in mainline and so
> should be in the OF device ID table in order to be matched and the proper
> modalias reported (once the I2C core is fixed).

I'd think we should fix the DTS files instead to contain a fallback we
agree on. Say, we agree on "atmel,at24c01" as a the generic fallback,
the DTS should contain:

	compatible = "<your_vendor>,<your_type>", "atmel,at24c01"

And we shall only keep compatible values in the source file which differ
in behaviour fromt the generic case.

> One option is to add #ifdef CONFIG_OF guards for the OF device table definition
> but again there's no agreement on that one since some maintainers say the it is
> better to always build the OF ID table than having #ifdefery in C code...

I don't like the #ifdeffery as well.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2017-03-15  7:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 15:16 [PATCH 0/4] misc: Add OF device table to I2C drivers that are missing it Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 1/4] misc: tsl2550: Add OF device ID table Javier Martinez Canillas
2017-03-14 20:53   ` Arnd Bergmann
2017-03-14 15:16 ` [PATCH 2/4] misc: ds1682: " Javier Martinez Canillas
2017-03-14 20:46   ` Arnd Bergmann
2017-03-15  0:38     ` Javier Martinez Canillas
2017-03-15  3:26       ` Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 3/4] eeprom: idt_89hpesx: " Javier Martinez Canillas
2017-03-14 15:16 ` [PATCH 4/4] eeprom: at24: " Javier Martinez Canillas
2017-03-14 22:59   ` Andy Shevchenko
2017-03-15  0:15     ` Javier Martinez Canillas
2017-03-15  7:58       ` Wolfram Sang [this message]
2017-03-15 10:58         ` Javier Martinez Canillas
2017-03-15 11:21           ` Andy Shevchenko
2017-03-15 11:39             ` Javier Martinez Canillas
2017-03-15 22:43               ` Andy Shevchenko
2017-03-16 12:28                 ` Javier Martinez Canillas
2017-03-16 13:07           ` Wolfram Sang
2017-03-16 13:13             ` Javier Martinez Canillas
2017-03-16 13:36               ` Wolfram Sang
2017-03-16 14:07                 ` Javier Martinez Canillas
2017-03-16 15:05                   ` Wolfram Sang
2017-03-16 15:39                     ` Javier Martinez Canillas
2017-03-20 16:45                       ` Javier Martinez Canillas

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=20170315075835.GA1438@katana \
    --to=wsa@the-dreams.de \
    --cc=andy.shevchenko@gmail.com \
    --cc=javier@osg.samsung.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox