All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mayuresh Chitale <mchitale@apm.com>
Cc: Jens Wiklander <jens.wiklander@linaro.org>, linux-acpi@vger.kernel.org
Subject: Re: ACPI support for optee driver
Date: Wed, 20 Sep 2017 13:39:18 +0300	[thread overview]
Message-ID: <20170920103918.GA4630@lahna.fi.intel.com> (raw)
In-Reply-To: <CAL-zptO3xg4k_B_S1SfKOghHGAUjqp56W9vqDdV3xgpUJ6b8dQ@mail.gmail.com>

On Wed, Sep 20, 2017 at 02:17:38PM +0530, Mayuresh Chitale wrote:
> Hi,
> 
> I am working on adding APCI support to optee kernel driver and was
> considering implementing it in the following way:
> 
> - An optee device node would be added to the bios as follows:
> Device(OPTE) {
>       Name(_HID, ...)
>       Name(_CID, ...)
>       Name(_DDN, ...)
>       Name (_DSD, Package () {
>           Package () {
>             Package (2) {"method", "smc"}
>           }

This _DSD is malformed as it is missing UUID.

>       })
>     }
> 
> - The optee kernel driver would then search for \\SB.OPTE device using
> acpi_get_handle and parse the node to get the conduit method.

You can use the standard device_property_* (see
include/linux/property.h) accessors which fully support _DSD device
properties.

> I was wondering if this is the correct way to implement it and if so
> do I need to get the OPTE device registered?  Your feedback is really
> appreciated.

There is something documented here:

Documentation/acpi/DSD-properties-rules.txt

  reply	other threads:[~2017-09-20 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20  8:47 ACPI support for optee driver Mayuresh Chitale
2017-09-20 10:39 ` Mika Westerberg [this message]
2017-09-20 16:37   ` Mayuresh Chitale
2017-09-21  6:44     ` Mika Westerberg

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=20170920103918.GA4630@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mchitale@apm.com \
    /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.