All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Thangavel <thangavel.k@hcl.com>
To: James Feist <james.feist@linux.intel.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: GPIO-Direction issue
Date: Fri, 13 Dec 2019 07:52:54 +0000	[thread overview]
Message-ID: <SG2PR04MB302998EE380A600959EB04DEFD540@SG2PR04MB3029.apcprd04.prod.outlook.com> (raw)
In-Reply-To: <b4de5043-0408-688b-f23b-396f7e21f0b1@linux.intel.com>

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

Sure. Thanks for your suggestions.


Thanks,
Kumar.
________________________________
From: James Feist <james.feist@linux.intel.com>
Sent: 12 December 2019 22:37
To: Kumar Thangavel <thangavel.k@hcl.com>; openbmc@lists.ozlabs.org <openbmc@lists.ozlabs.org>
Subject: Re: GPIO-Direction issue

On 12/11/19 4:50 AM, Kumar Thangavel wrote:
> Hi All,
>
>          I am using entity manager configuration file(.json) to enable
> the GPIO pin.
>
>          The gpio node was created in /sys/class/gpio/* using
> configuration files.
>
>          I set Direction as "Out" in json. But it was not getting
> changed in /sys/class/gpio/gpio*/Direction. The Direction was still
> remains as "in".

Gpio usage via sysfs is deprecated. We're currently working to remove
all usages of it ourselves that we have in entity-manager. I would
suggest using libgpiod to use gpio via character device instead.

https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flibs%2Flibgpiod%2Flibgpiod.git%2Ftree%2Fbindings%2Fcxx&amp;data=02%7C01%7Cthangavel.k%40hcl.com%7Cbf18dac88ecc4a35bc2508d77f25bb67%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637117672349243185&amp;sdata=Jeruefedzy4Bnb%2FIVjn4j1zT4YUhh9KwEH1tB6oNKxQ%3D&amp;reserved=0

::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

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

      reply	other threads:[~2019-12-13  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11 12:50 GPIO-Direction issue Kumar Thangavel
2019-12-12 17:07 ` James Feist
2019-12-13  7:52   ` Kumar Thangavel [this message]

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=SG2PR04MB302998EE380A600959EB04DEFD540@SG2PR04MB3029.apcprd04.prod.outlook.com \
    --to=thangavel.k@hcl.com \
    --cc=james.feist@linux.intel.com \
    --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.