linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Eason Yen <eason.yen@mediatek.com>
Cc: linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
	devicetree@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v2] soc: mediatek: add SMC fid table for SIP interface
Date: Mon, 11 Nov 2019 16:17:30 +0100	[thread overview]
Message-ID: <71b9cfcc-bd4f-75de-0057-d64c5dc49e92@gmail.com> (raw)
In-Reply-To: <1573439402-16249-1-git-send-email-eason.yen@mediatek.com>



On 11/11/2019 03:30, Eason Yen wrote:
> soc: mediatek: add SMC fid table for SIP interface
> 
> 1. Add a header file to provide SIP interface to ATF
>    for clients, please define MTK_SIP_XXX  with specific ID
> 
> 2. Add AUDIO SMC fid
>    mtk sip call example:
>    arm_smccc_smc(MTK_SIP_AUDIO_CONTROL,
>                  MTK_AUDIO_SMC_OP_DRAM_REQUEST,
>                  0, 0, 0, 0, 0, 0, &res)

Are you planning to upstream a driver consuming this interface?
If so, I propose to add this patch to the submission of the driver. Sounds good?

Regards,
Matthias

> 
> 
> Eason Yen (1):
>   soc: mediatek: add SMC fid table for SIP interface
> 
>  include/linux/soc/mediatek/mtk_sip_svc.h |   28 ++++++++++++++++++++++++++++
>  1 file changed, 28 insertions(+)
>  create mode 100644 include/linux/soc/mediatek/mtk_sip_svc.h
> 

  parent reply	other threads:[~2019-11-11 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  2:30 [PATCH v2] soc: mediatek: add SMC fid table for SIP interface Eason Yen
2019-11-11  2:30 ` [PATCH v2 1/1] " Eason Yen
2019-11-11 15:17 ` Matthias Brugger [this message]
2019-11-12  8:00   ` [PATCH v2] " Eason Yen
2019-11-12 13:15     ` Matthias Brugger

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=71b9cfcc-bd4f-75de-0057-d64c5dc49e92@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eason.yen@mediatek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=wsd_upstream@mediatek.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 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).