public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	Alexander Kolesnikov <akolesni@codeaurora.org>,
	Konstantin Dorfman <kdorfman@codeaurora.org>
Subject: Re: char interface to sdio, chdio.c
Date: Wed, 16 Jul 2014 16:08:11 -0700	[thread overview]
Message-ID: <53C705DB.3040700@codeaurora.org> (raw)
In-Reply-To: <53C6D4B6.3030506@codeaurora.org>

On 07/16/14 12:38, Stephen Boyd wrote:
> On 07/16/14 11:44, Greg KH wrote:
>> My specific question is why 2 different interfaces?
> Ok. It definitely looks odd to support set/get of the VDD with sysfs and
> ioctl interfaces. I'm just guessing, but I suspect it's a permissions
> thing given that the patch that introduces the VDD stuff also updates
> the permissions of the device node. Of course, the commit text only
> mentions an ioctl, nothing about sysfs. The only other sysfs stuff seems
> to be module parameters to change the vendor ids.
>
> I'll have to go repo diving to figure out if the sysfs interface was
> ever used. Maybe Alex or Konstantin can respond before I have to do that.
>
>

I couldn't find any usage of the sysfs interface. The only thing I see
used is the host_name field when the module is inserted, if that even
happens at all (I'm not sure because it's behind some ifdef that may or
may not be defined). Sorry this doesn't explain why there are two
different interfaces for the VDD stuff. Hopefully Alex or Konstantin can
help.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation


  reply	other threads:[~2014-07-16 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16  3:26 char interface to sdio, chdio.c Greg KH
2014-07-16 18:21 ` Stephen Boyd
2014-07-16 18:44   ` Greg KH
2014-07-16 19:38     ` Stephen Boyd
2014-07-16 23:08       ` Stephen Boyd [this message]
2014-07-16 23:11         ` Greg KH
2014-07-17  5:33         ` Greg KH
2014-07-17 10:17           ` Arnd Bergmann
2014-07-18  3:08             ` Greg KH

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=53C705DB.3040700@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=akolesni@codeaurora.org \
    --cc=greg@kroah.com \
    --cc=kdorfman@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    /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