[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ziv62bzb.fsf@ashishki-desk.ger.corp.intel.com>
Date: Fri, 12 Feb 2016 17:18:48 +0200
From: Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To: Chunyan Zhang <zhang.chunyan@...aro.org>,
mathieu.poirier@...aro.org
Cc: mike.leach@....com, Michael.Williams@....com, al.grant@....com,
tor@...com, nicolas.guion@...com, broonie@...nel.org,
robh@...nel.org, pratikp@...eaurora.org, corbet@....net,
mark.rutland@....com, zhang.lyra@...il.com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-api@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH V3 1/6] stm class: Add ioctl get_options interface
Chunyan Zhang <zhang.chunyan@...aro.org> writes:
> There is already an interface of set_options, but no get_options yet.
> Before setting any options, one would may want to see the current
> status of that option by means of get_options interface. This
> interface has been used in CoreSight STM driver.
I'm not sure I understand the reasoning behind this. If a userspace
program opens a communication channel and wants to configure certain
features on it, why does its choice depend on what has been configured
for this channel previously? It can be anything at all. Most likely,
it's either unconfigured or configured to its default values, but why
does this matter for a new writer?
Regards,
--
Alex
Powered by blists - more mailing lists