From: Tony <tony.makkiel@daqri.com>
To: linux-acpi@vger.kernel.org
Subject: Any acpi_device_id naming conventions to follow?
Date: Mon, 27 Jun 2016 12:36:47 +0100 [thread overview]
Message-ID: <57710FCF.3090908@daqri.com> (raw)
Hi all,
Is there a naming convention to follow on ACPI device names
(acpi_device_id) for device drivers?
For TI led lp3952, I would otherwise name it as "lp3952". But in order
to follow ACPI/PNP device ID convention, it has to be 7 or 8 char long.
So is "TLP3952" a valid name?
Should the name be registered before it can be used? If it has to be
registered, is there a subset of characters which can be used without
registration?
From a little bit of googling, I found there is an ACPI ID 'TXNW' for TI,
http://www.uefi.org/ACPI_ID_List?search=texas
So should the device name be "TXNW3952"?
Many Thanks,
Tony
next reply other threads:[~2016-06-27 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 11:36 Tony [this message]
2016-06-28 12:05 ` Any acpi_device_id naming conventions to follow? Rafael J. Wysocki
2016-06-28 12:17 ` Tony
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=57710FCF.3090908@daqri.com \
--to=tony.makkiel@daqri.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 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).