[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5583D130.5080207@linaro.org>
Date: Fri, 19 Jun 2015 09:22:08 +0100
From: Daniel Thompson <daniel.thompson@...aro.org>
To: Sagar Dharia <sdharia@...eaurora.org>, gregkh@...uxfoundation.org,
bp@...e.de, poeschel@...onage.de, treding@...dia.com,
broonie@...nel.org, gong.chen@...ux.intel.com,
andreas.noever@...il.com, alan@...ux.intel.com,
mathieu.poirier@...aro.org, daniel@...ll.ch, oded.gabbay@....com,
jkosina@...e.cz, sharon.dvir1@...l.huji.ac.il, joe@...ches.com,
davem@...emloft.net, james.hogan@...tec.com,
michael.opdenacker@...e-electrons.com, linux-kernel@...r.kernel.org
CC: nkaje@...eaurora.org, kheitke@...ience.com, mlocke@...eaurora.org,
agross@...eaurora.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH V2 1/6] SLIMbus: Device management on SLIMbus
On 17/06/15 02:45, Sagar Dharia wrote:
> --- /dev/null
> +++ b/drivers/slimbus/Kconfig
> @@ -0,0 +1,9 @@
> +#
> +# SLIMBUS driver configuration
> +#
> +menuconfig SLIMBUS
> + tristate "Slimbus support"
> + help
> + Slimbus is standard interface between baseband and audio codec,
> + and other peripheral components in mobile terminals.
Perhaps this is a fussy comment but this description of slimbus makes
pretty heavy use of mobile phone jargon. Admittedly it is jargon from
the slimbus spec which, as standards go, seems rather myopic about its
potential user base.
However, even the standards own self-description doesn't limit its role
to baseband <-> peripherals. What happened to the application
processor/main-SoC?
Also would an "If unsure, choose N." be useful? It could be quite a long
time before someone who doesn't know they need slimbus actually finds
that they do.
Daniel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists