linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merez@codeaurora.org
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Maya Erez <merez@codeaurora.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] mmc: card: Move MMC specific attributes to mmc sub-directory
Date: Thu, 12 Jul 2012 13:55:50 -0700 (PDT)	[thread overview]
Message-ID: <e5346013f62b4eb6587b2bd99a77f007.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1341231337-6921-2-git-send-email-merez@codeaurora.org>

Hi Chris,

Can we push this change to mmc-next?

Thanks,
Maya
On Mon, July 2, 2012 5:15 am, Maya Erez wrote:
> Separate MMC specific attributes from general block device
> attributes and move them from the /sys/block/<BLOCK_DEV> directory
> to /sys/block/<BLOCK_DEV>/mmc directory
>
> Signed-off-by: Maya Erez <merez@codeaurora.org>
>
> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
> index c965f2b..c23034d 100644
> --- a/drivers/mmc/card/block.c
> +++ b/drivers/mmc/card/block.c
> @@ -114,6 +114,9 @@ struct mmc_blk_data {
>  	struct device_attribute force_ro;
>  	struct device_attribute power_ro_lock;
>  	int	area_type;
> +
> +	struct kobject kobj;
> +	struct kobj_type kobj_type;
>  };
>
>  static DEFINE_MUTEX(open_lock);
> @@ -185,6 +188,51 @@ static void mmc_blk_put(struct mmc_blk_data *md)
>  	mutex_unlock(&open_lock);
>  }
>
> +static ssize_t mmc_blk_attr_show(struct kobject *kobj, struct attribute
> *attr,
> +			    char *buf)
> +{
> +	struct device_attribute *dev_attr;
> +	struct mmc_blk_data *md;
> +	ssize_t ret;
> +
> +	dev_attr = container_of(attr, struct device_attribute, attr);
> +	if (!dev_attr->show)
> +		return -EIO;
> +
> +	md = container_of(kobj, struct mmc_blk_data, kobj);
> +	if (!md || &md->kobj != kobj)
> +		return -EINVAL;
> +
> +	ret = dev_attr->show(disk_to_dev(md->disk), dev_attr, buf);
> +
> +	return ret;
> +}
> +
> +static ssize_t mmc_blk_attr_store(struct kobject *kobj, struct attribute
> *attr,
> +			    const char *buf, size_t count)
> +{
> +	struct device_attribute *dev_attr;
> +	struct mmc_blk_data *md;
> +	ssize_t ret;
> +
> +	dev_attr = container_of(attr, struct device_attribute, attr);
> +	if (!dev_attr->store)
> +		return -EIO;
> +
> +	md = container_of(kobj, struct mmc_blk_data, kobj);
> +	if (!md || &md->kobj != kobj)
> +		return -EINVAL;
> +
> +	ret = dev_attr->store(disk_to_dev(md->disk), dev_attr, buf, count);
> +
> +	return ret;
> +}
> +
> +static const struct sysfs_ops mmc_blk_sysfs_ops = {
> +	.show	= mmc_blk_attr_show,
> +	.store	= mmc_blk_attr_store,
> +};
> +
>  static ssize_t power_ro_lock_show(struct device *dev,
>  		struct device_attribute *attr, char *buf)
>  {
> @@ -2004,14 +2052,15 @@ static void mmc_blk_remove_req(struct mmc_blk_data
> *md)
>  	if (md) {
>  		card = md->queue.card;
>  		if (md->disk->flags & GENHD_FL_UP) {
> -			device_remove_file(disk_to_dev(md->disk), &md->force_ro);
> +			sysfs_remove_file(&md->kobj, &md->force_ro.attr);
>  			if ((md->area_type & MMC_BLK_DATA_AREA_BOOT) &&
>  					card->ext_csd.boot_ro_lockable)
> -				device_remove_file(disk_to_dev(md->disk),
> -					&md->power_ro_lock);
> +				sysfs_remove_file(&md->kobj,
> +					&md->power_ro_lock.attr);
>
>  			/* Stop new requests from getting into the queue */
>  			del_gendisk(md->disk);
> +			kobject_put(&md->kobj);
>  		}
>
>  		/* Then flush out any already in there */
> @@ -2040,12 +2089,19 @@ static int mmc_add_disk(struct mmc_blk_data *md)
>  	struct mmc_card *card = md->queue.card;
>
>  	add_disk(md->disk);
> +
> +	md->kobj_type.sysfs_ops = &mmc_blk_sysfs_ops;
> +	ret = kobject_init_and_add(&md->kobj, &md->kobj_type,
> +		    &disk_to_dev(md->disk)->kobj, "%s", "mmc");
> +	if (ret)
> +		goto init_kobj_fail;
> +
>  	md->force_ro.show = force_ro_show;
>  	md->force_ro.store = force_ro_store;
>  	sysfs_attr_init(&md->force_ro.attr);
>  	md->force_ro.attr.name = "force_ro";
>  	md->force_ro.attr.mode = S_IRUGO | S_IWUSR;
> -	ret = device_create_file(disk_to_dev(md->disk), &md->force_ro);
> +	ret = sysfs_create_file(&md->kobj, &md->force_ro.attr);
>  	if (ret)
>  		goto force_ro_fail;
>
> @@ -2064,16 +2120,17 @@ static int mmc_add_disk(struct mmc_blk_data *md)
>  		md->power_ro_lock.attr.mode = mode;
>  		md->power_ro_lock.attr.name =
>  					"ro_lock_until_next_power_on";
> -		ret = device_create_file(disk_to_dev(md->disk),
> -				&md->power_ro_lock);
> +		ret = sysfs_create_file(&md->kobj, &md->power_ro_lock.attr);
>  		if (ret)
>  			goto power_ro_lock_fail;
>  	}
>  	return ret;
>
>  power_ro_lock_fail:
> -	device_remove_file(disk_to_dev(md->disk), &md->force_ro);
> +	sysfs_remove_file(&md->kobj, &md->force_ro.attr);
>  force_ro_fail:
> +	kobject_put(&md->kobj);
> +init_kobj_fail:
>  	del_gendisk(md->disk);
>
>  	return ret;
> --
> 1.7.3.3
> --
> Sent by a consultant of the Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
>


-- 
Sent by consultant of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum

      reply	other threads:[~2012-07-12 20:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02 12:15 [PATCH v4 1/2] mmc: card: Move MMC specific attributes to mmc sub-directory Maya Erez
2012-07-12 20:55 ` merez [this message]

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=e5346013f62b4eb6587b2bd99a77f007.squirrel@www.codeaurora.org \
    --to=merez@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;
as well as URLs for NNTP newsgroup(s).