public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
To: Javier Martinez Canillas
	<javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
Cc: Lennart Poettering
	<lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org>,
	Brian Norris
	<briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	Sjoerd Simons
	<sjoerd.simons-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.org>,
	linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: modalias for OF-declared I2C/SPI devices
Date: Fri, 11 Aug 2017 10:14:29 +0200	[thread overview]
Message-ID: <20170811081429.GA9957@wunner.de> (raw)

Hi Javier,

you proposed an RFC patch a while ago which lets the I2C and SPI core
report an "of:" modalias to user space for devices declared in a
device tree (vs. a legacy machine description), instead of an "i2c:"
or "spi:" modalias:

https://lkml.org/lkml/2014/9/11/458
https://lkml.org/lkml/2015/8/20/98

I justed wanted to ask what the status of the patch is?  Looking at
linux-next I notice that you've been fixing up drivers, machine
descriptions and device trees as recently as July.  Apparently you're
still busy landing all the prep work necessary for the patch, is that
correct?

It seems to be an awful lot of work cleaning up this mess and I assume
there is plenty of out-of-tree stuff that may break once the patch lands,
so I've been wondering if a simpler solution might be to change user
space, given that we already communicate all the OF_COMPATIBLE_* uevent
variables.  So I opened an issue for systemd-udevd but so far Lennart
remains unconvinced:

https://github.com/systemd/systemd/issues/6555

I still think that evaluation of OF_COMPATIBLE_* by user space would be
the best solution since it seems impossible to cram the degrees of
freedom afforded by compatible strings into a single modalias string.

The reason I came across this issue is that module autoloading fails for
drivers/gpio/gpio-74x164.c as it only declares an "of" MODULE_DEVICE_TABLE.
I was going to upstream a GPIO and an IIO driver, both SPI-based, and was
wondering what the current best practice is:  Should I only declare an
"of" MODULE_DEVICE_TABLE or should I also provide an "spi"
MODULE_DEVICE_TABLE?

Thanks!

Lukas
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-08-11  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  8:14 Lukas Wunner [this message]
     [not found] ` <20170811081429.GA9957-JFq808J9C/izQB+pC5nmwQ@public.gmane.org>
2017-08-11 14:11   ` modalias for OF-declared I2C/SPI devices Javier Martinez Canillas
     [not found]     ` <1fcd1d99-39ca-6db6-51fc-148c84f66297-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-08-14  9:20       ` Mark Brown

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=20170811081429.GA9957@wunner.de \
    --to=lukas-jfq808j9c/izqb+pc5nmwq@public.gmane.org \
    --cc=briannorris-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=javier-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org \
    --cc=lennart-mdGvqq1h2p+GdvJs77BJ7Q@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sjoerd.simons-ZGY8ohtN/8pPYcu2f3hruQ@public.gmane.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