mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hauke Mehrtens <hauke@hauke-m.de>
To: Matt Redfearn <matt.redfearn@imgtec.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mips@linux-mips.org, linux-remoteproc@vger.kernel.org,
	lisa.parratt@imgtec.com, linux-kernel@vger.kernel.org,
	olaf.wachendorf@intel.com, hauke.mehrtens@intel.com
Subject: Re: [PATCH v3 4/4] MIPS: Deprecate VPE Loader
Date: Wed, 12 Oct 2016 13:09:37 +0200	[thread overview]
Message-ID: <c4d01a54-7a68-c9ee-bc5c-ac01743f7269@hauke-m.de> (raw)
In-Reply-To: <1476193356-1350-5-git-send-email-matt.redfearn@imgtec.com>

This interface is currently used by the Intel / Lantiq voice Firmware.
This firmware is used by all Intel / Lantiq MIPS SoCs when they should
support analog voice.

What is the proposed timeline for the removal of this interface?

Hauke

On 10/11/2016 03:42 PM, Matt Redfearn wrote:
> The MIPS remote processor driver (CONFIG_MIPS_RPROC) provides a more
> standard mechanism for using one or more VPs as coprocessors running
> separate firmware.
> 
> Here we deprecate this mechanism before it is removed.
> 
> Signed-off-by: Matt Redfearn <matt.redfearn@imgtec.com>
> ---
> 
> Changes in v3: None
> Changes in v2: None
> 
>  arch/mips/Kconfig | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index fd2468e71e63..3e767c373c7b 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -2264,7 +2264,7 @@ comment "MIPS R2-to-R6 emulator is only available for UP kernels"
>  	depends on SMP && CPU_MIPSR6
>  
>  config MIPS_VPE_LOADER
> -	bool "VPE loader support."
> +	bool "VPE loader support (DEPRECATED)"
>  	depends on SYS_SUPPORTS_MULTITHREADING && MODULES
>  	select CPU_MIPSR2_IRQ_VI
>  	select CPU_MIPSR2_IRQ_EI
> @@ -2273,6 +2273,9 @@ config MIPS_VPE_LOADER
>  	  Includes a loader for loading an elf relocatable object
>  	  onto another VPE and running it.
>  
> +	  Unless you have a specific need, you should use CONFIG_MIPS_RPROC
> +          instead of this.
> +
>  config MIPS_VPE_LOADER_CMP
>  	bool
>  	default "y"
> 

  reply	other threads:[~2016-10-12 11:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-11 13:42 [PATCH v3 0/4] MIPS: Remote processor driver Matt Redfearn
2016-10-11 13:42 ` [PATCH v3 1/4] irqchip: mips-gic: Add context saving for MIPS_REMOTEPROC Matt Redfearn
2016-10-11 13:42 ` [PATCH v3 2/4] MIPS: CPS: Add VP(E) stealing Matt Redfearn
2016-10-11 13:42 ` [PATCH v3 3/4] remoteproc/MIPS: Add a remoteproc driver for MIPS Matt Redfearn
2016-10-11 13:42 ` [PATCH v3 4/4] MIPS: Deprecate VPE Loader Matt Redfearn
2016-10-12 11:09   ` Hauke Mehrtens [this message]
2016-10-17 11:01     ` Matt Redfearn
2016-10-17 21:13 ` [PATCH v3 0/4] MIPS: Remote processor driver Hauke Mehrtens
2016-10-18 14:30   ` Matt Redfearn

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=c4d01a54-7a68-c9ee-bc5c-ac01743f7269@hauke-m.de \
    --to=hauke@hauke-m.de \
    --cc=bjorn.andersson@linaro.org \
    --cc=hauke.mehrtens@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=lisa.parratt@imgtec.com \
    --cc=matt.redfearn@imgtec.com \
    --cc=ohad@wizery.com \
    --cc=olaf.wachendorf@intel.com \
    --cc=ralf@linux-mips.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®