linux-mips
[Top] [All Lists]

Re: [PATCH] MIPS: Make CP0 config registers readable via sysfs.

To: "Hill, Steven" <sjhill@mips.com>
Subject: Re: [PATCH] MIPS: Make CP0 config registers readable via sysfs.
From: Lars-Peter Clausen <lars@metafoo.de>
Date: Wed, 12 Dec 2012 19:49:56 +0100
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
In-reply-to: <31E06A9FC96CEC488B43B19E2957C1B801146AA779@exchdb03.mips.com>
List-archive: <http://www.linux-mips.org/archives/linux-mips/>
List-help: <mailto:ecartis@linux-mips.org?Subject=help>
List-id: linux-mips <linux-mips.eddie.linux-mips.org>
List-owner: <mailto:ralf@linux-mips.org>
List-post: <mailto:linux-mips@linux-mips.org>
List-software: Ecartis version 1.0.0
List-subscribe: <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips>
List-unsubscribe: <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips>
References: <1354858280-29576-1-git-send-email-sjhill@mips.com>,<50C89870.5000704@metafoo.de> <31E06A9FC96CEC488B43B19E2957C1B801146AA779@exchdb03.mips.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121027 Icedove/3.0.11
On 12/12/2012 05:44 PM, Hill, Steven wrote:
> Lars,
> 
> This patch was requested by our DSP/Codec group to help with selecting the 
> best user-space codecs at runtime. Simply reading /proc/cpuinfo was 
> insufficient. I posted this patch more for feedback and interest with minimal 
> expectations that it would make it upstream. This patch will always be in our 
> supported branches, but I will defer to everyone else on its worth for 
> upstream.
> 
> -Steve

Well if it is something that is useful it makes sense to upstream it,
especially if you are developing applications. Many people before you have
learned the hard way that stashing stuff away in their private branches was not
the best idea. If you are smart you are going to avoid that.

It may not be the best solution though to just dump all the cp register to
userspace. As Florian suggested there might be a smarter way to solve this.

- Lars

<Prev in Thread] Current Thread [Next in Thread>