From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Platform Driver <platform-driver-x86@vger.kernel.org>
Subject: How to inject fwnode/oftree/acpi data by platform driver ?
Date: Sat, 1 Jun 2019 16:14:09 +0200 [thread overview]
Message-ID: <c15a9872-4ad4-1b7e-e34f-14549b5b55eb@metux.net> (raw)
Hi folks,
I'm looking for a way to inject fwnode data from a platform driver,
in order to initialize generic drivers w/ board specific configuration.
The idea is getting rid of passing driver specific pdata structs
(which, IIRC, seem to be deprecated).
An example usecase is the APUv2/3 board, which have things like gpios
wired to buttons and LEDs. The board can only be detected via DMI
string, no way to probe the platform devices - have to be initialized
explicitly (that's how I'm already doing it now).
The nicest way, IMHO, would be if I could just write some piece of DTS
and some fancy magic all the rest under the hood. Such thing doesn't
seem to exist yet. Does it make sense to implement that ? How could
we do it ?
Which other options do we have ?
Or should we just leave everything as it is and stick w/ pdata structs ?
thx
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next reply other threads:[~2019-06-01 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 14:14 Enrico Weigelt, metux IT consult [this message]
2019-06-11 18:44 ` Andy Shevchenko
2019-06-12 8:01 ` Heikki Krogerus
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=c15a9872-4ad4-1b7e-e34f-14549b5b55eb@metux.net \
--to=lkml@metux.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®