public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Amitkumar Karwar <akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
To: "linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Ulf Hansson <ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: Nishant Sarmukadam
	<nishants-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
	Wei-Ning Huang <wnhuang-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	"linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Cathy Luo <cluo-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>,
	Xinming Hu <huxm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
Subject: RE: [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size
Date: Thu, 22 Dec 2016 09:09:50 +0000	[thread overview]
Message-ID: <1fa11bbfaf554dc2961893efbf135710@SC-EXCH04.marvell.com> (raw)
In-Reply-To: <1466069006-10757-1-git-send-email-akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>

Hi Ulf,

> From: Amitkumar Karwar [mailto:akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org]
> Sent: Thursday, June 16, 2016 2:53 PM
> To: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Cc: Nishant Sarmukadam; Wei-Ning Huang; linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org;
> Cathy Luo; Xinming Hu; Amitkumar Karwar
> Subject: [PATCH v4 1/2] mmc: API for accessing host supported maximum
> segment count and size
> 
> From: Xinming Hu <huxm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
> 
> sdio device drivers need be able to get the host supported max_segs and
> max_seg_size, so that they know the buffer size to allocate while
> utilizing the scatter/gather DMA buffer list.
> 
> This patch provides API for this purpose.
> 
> Signed-off-by: Xinming Hu <huxm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
> Signed-off-by: Amitkumar Karwar <akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
> ---
> v2: v2 was submitted with minor improvement like replacing BUG_ON()
> with WARN_ON()
> v3: Addressed below review comments from Ulf Hansson
>     a) In v3, patch has been split into two separate patches.
>     b) Patch 1/2 introduces an API to fetch max_seg_size and max_segs
>     c) Replaced WARN_ON() with proper error code when sg_ptr->length is
> invalid
>     d) Instead of duplicating the code in mmc_io_rw_extended(), extra
> bool parameter
>        has been added to this function and used it in new APIs for SG.
> v4: Removed WARN_ON() calls in newly added APIs. It's gets called in
> probe handler.
>     Caller already takes care of it(Shawn Lin).
> ---
>  drivers/mmc/core/sdio_io.c                          | 21
> +++++++++++++++++++++
>  .../wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c   |  6 +++---
>  include/linux/mmc/sdio_func.h                       |  3 +++
>  3 files changed, 27 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/mmc/core/sdio_io.c b/drivers/mmc/core/sdio_io.c
> index 78cb4d5..b1ecacc 100644
> --- a/drivers/mmc/core/sdio_io.c
> +++ b/drivers/mmc/core/sdio_io.c
> @@ -720,3 +720,24 @@ int sdio_set_host_pm_flags(struct sdio_func *func,
> mmc_pm_flag_t flags)
>  	return 0;
>  }
>  EXPORT_SYMBOL_GPL(sdio_set_host_pm_flags);
> +
> +/**
> + *	sdio_get_host_max_seg_size - get host maximum segment size
> + *	@func: SDIO function attached to host
> + */
> +unsigned int sdio_get_host_max_seg_size(struct sdio_func *func) {
> +	return func->card->host->max_seg_size; }
> +EXPORT_SYMBOL_GPL(sdio_get_host_max_seg_size);
> +
> +/**
> + *	sdio_get_host_max_seg_count - get host maximum segment count
> + *	@func: SDIO function attached to host
> + */
> +unsigned short sdio_get_host_max_seg_count(struct sdio_func *func) {
> +	return func->card->host->max_segs;
> +}
> +EXPORT_SYMBOL_GPL(sdio_get_host_max_seg_count);
> +
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> index c4b89d2..ba579f4 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bcmsdh.c
> @@ -896,9 +896,9 @@ void brcmf_sdiod_sgtable_alloc(struct
> brcmf_sdio_dev *sdiodev)
>  	max_blocks = min_t(uint, host->max_blk_count, 511u);
>  	sdiodev->max_request_size = min_t(uint, host->max_req_size,
>  					  max_blocks * func->cur_blksize);
> -	sdiodev->max_segment_count = min_t(uint, host->max_segs,
> -					   SG_MAX_SINGLE_ALLOC);
> -	sdiodev->max_segment_size = host->max_seg_size;
> +	sdiodev->max_segment_count = min_t(uint, SG_MAX_SINGLE_ALLOC,
> +					   sdio_get_host_max_seg_count(func));
> +	sdiodev->max_segment_size = sdio_get_host_max_seg_size(func);
> 
>  	if (!sdiodev->sg_support)
>  		return;
> diff --git a/include/linux/mmc/sdio_func.h
> b/include/linux/mmc/sdio_func.h index aab032a..b2b91df 100644
> --- a/include/linux/mmc/sdio_func.h
> +++ b/include/linux/mmc/sdio_func.h
> @@ -159,4 +159,7 @@ extern void sdio_f0_writeb(struct sdio_func *func,
> unsigned char b,  extern mmc_pm_flag_t sdio_get_host_pm_caps(struct
> sdio_func *func);  extern int sdio_set_host_pm_flags(struct sdio_func
> *func, mmc_pm_flag_t flags);
> 
> +unsigned short sdio_get_host_max_seg_count(struct sdio_func *func);
> +unsigned int sdio_get_host_max_seg_size(struct sdio_func *func);
> +
>  #endif /* LINUX_MMC_SDIO_FUNC_H */

This has been pending for a while.
Any further review comments on this v4 patch series?

Regards,
Amitkumar Karwar

  parent reply	other threads:[~2016-12-22  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-16  9:23 [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size Amitkumar Karwar
2016-06-16  9:23 ` [PATCH v4 2/2] mmc: sdio support external scatter gather list Amitkumar Karwar
2016-08-09 10:16 ` [PATCH v4 1/2] mmc: API for accessing host supported maximum segment count and size Amitkumar Karwar
2017-11-16 13:57   ` Xinming Hu
2017-11-21 11:44     ` Ulf Hansson
2017-11-21 11:58       ` [EXT] " Xinming Hu
2017-11-21 15:13         ` Ulf Hansson
2017-11-22  1:58           ` Xinming Hu
     [not found] ` <1466069006-10757-1-git-send-email-akarwar-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org>
2016-12-22  9:09   ` Amitkumar Karwar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-22  0:52 Xu (Shanghai) Wang

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=1fa11bbfaf554dc2961893efbf135710@SC-EXCH04.marvell.com \
    --to=akarwar-eyqppykdwxrbdgjk7y7tuq@public.gmane.org \
    --cc=cluo-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
    --cc=huxm-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-mmc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nishants-eYqpPyKDWXRBDgjK7y7TUQ@public.gmane.org \
    --cc=ulf.hansson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=wnhuang-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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