All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oskar Senft <osk@google.com>
To: "Bills, Jason M" <jason.m.bills@linux.intel.com>
Cc: Michael Richardson <mcr@sandelman.ca>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: x86-power-control
Date: Thu, 17 Oct 2019 13:21:42 -0400	[thread overview]
Message-ID: <CABoTLcRsJSSeB81jx-7WCXAfrB2CvB+ZbXvnmPxCaikCVpu=0Q@mail.gmail.com> (raw)
In-Reply-To: <cd3563fd-47bb-2c09-beda-5ce5ba8c8aa0@linux.intel.com>

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

Hi Jason


> In our DTS we use gpio-line-names to name all of the GPIOs in one block:
>
> &gpio {
>         status = "okay";
>         gpio-line-names =
> [...]
>         /*D0-D7*/       "","","","","","","","",
>         /*E0-E7*/
>  "RESET_BUTTON","RESET_OUT","POWER_BUTTON","POWER_OUT","","","","",
>         /*F0-F7*/       "NMI_OUT","","","","CPU_ERR0","CPU_ERR1","","",
>         /*G0-G7*/
>  "CPU_ERR2","CPU_CATERR","PCH_BMC_THERMTRIP","","","","","",
>

Ugh, ok - that's a nice trick. But it's also a little messy :-/ Is that the
"officially recommended" way? I guess, since the other option I tried
doesn't work!.

Is that purely used for naming lines, or does it have any semantic impact?

Thanks
Oskar.

[-- Attachment #2: Type: text/html, Size: 1450 bytes --]

  reply	other threads:[~2019-10-17 17:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  1:13 x86-power-control Vijay Khemka
2019-10-17  9:56 ` x86-power-control Michael Richardson
2019-10-17 13:38   ` x86-power-control Oskar Senft
2019-10-17 16:02     ` x86-power-control Bills, Jason M
2019-10-17 17:21       ` Oskar Senft [this message]
2019-10-17 19:05         ` x86-power-control Bills, Jason M
2019-10-17 22:13     ` x86-power-control Vijay Khemka
2019-10-17 22:08   ` x86-power-control Vijay Khemka
2019-10-18  6:43     ` x86-power-control Michael Richardson
2019-10-17 16:01 ` x86-power-control Bills, Jason M
2019-10-17 22:32   ` x86-power-control Vijay Khemka
2019-10-17 23:25     ` x86-power-control Bills, Jason M
2019-10-17 23:52       ` x86-power-control Vijay Khemka
2019-10-18 18:00         ` x86-power-control Bills, Jason M
2019-10-18 23:04           ` x86-power-control Vijay Khemka
2019-10-21 23:03             ` x86-power-control Bills, Jason M
2019-10-22  1:15               ` x86-power-control Vijay Khemka
2019-10-22 17:14                 ` x86-power-control Bills, Jason M
2019-10-22 17:46                   ` x86-power-control Vijay Khemka
2019-10-22 17:56                     ` x86-power-control James Feist
2019-10-22 18:04                       ` x86-power-control Johnathan Mantey
2019-10-22 19:06                         ` x86-power-control Johnathan Mantey
2019-10-22 19:12                           ` x86-power-control James Feist
2019-10-23 16:35                         ` x86-power-control Vijay Khemka
2019-11-02  0:33 x86-power-control Vijay Khemka
2019-11-04 19:52 ` x86-power-control Bills, Jason M
2019-11-05  0:33   ` x86-power-control Vijay Khemka

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='CABoTLcRsJSSeB81jx-7WCXAfrB2CvB+ZbXvnmPxCaikCVpu=0Q@mail.gmail.com' \
    --to=osk@google.com \
    --cc=jason.m.bills@linux.intel.com \
    --cc=mcr@sandelman.ca \
    --cc=openbmc@lists.ozlabs.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.