public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Kim <jh4u.kim@samsung.com>
To: linux-mmc@vger.kernel.org
Cc: ulf.hansson@linaro.org, 'Jaehoon Chung' <jh80.chung@samsung.com>
Subject: [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES
Date: Wed, 19 Oct 2016 20:31:46 +0900	[thread overview]
Message-ID: <0d4301d229fc$607a9770$216fc650$@samsung.com> (raw)

>From 27d46f5697434542ad9cafbc6a9630dc14915f91 Mon Sep 17 00:00:00 2001
From: Jeonghan Kim <jh4u.kim@samsung.com>
Date: Wed, 19 Oct 2016 19:48:02 +0900
Subject: [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES

It is used for limitation of buffer size during IOCTL such as FFU.
However, eMMC FW size is bigger than (512L*256).
(For instance, currently, Samsung eMMC FW size is over 300KB.)
So, it needs to increase to execute FFU.

Signed-off-by: Jeonghan Kim <jh4u.kim@samsung.com>
---
 include/uapi/linux/mmc/ioctl.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/uapi/linux/mmc/ioctl.h b/include/uapi/linux/mmc/ioctl.h
index 7e385b8..700a551 100644
--- a/include/uapi/linux/mmc/ioctl.h
+++ b/include/uapi/linux/mmc/ioctl.h
@@ -69,6 +69,6 @@ struct mmc_ioc_multi_cmd {
  * is enforced per ioctl call.  For larger data transfers, use the normal
  * block device operations.
  */
-#define MMC_IOC_MAX_BYTES  (512L * 256)
+#define MMC_IOC_MAX_BYTES  (512L * 1024)
 #define MMC_IOC_MAX_CMDS    255
 #endif /* LINUX_MMC_IOCTL_H */
--
1.9.1



             reply	other threads:[~2016-10-19 15:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20161019113147epcas1p23270c03a8ea440a88dd0d6ab85af8051@epcas1p2.samsung.com>
2016-10-19 11:31 ` Jeremy Kim [this message]
2016-10-21  6:38   ` [PATCH] mmc: block: Change MMC_IOC_MAX_BYTES Jaehoon Chung
2016-10-21  8:21   ` Ulf Hansson
     [not found] <CGME20161018103940epcas1p1da351e49f18c5707eea3b817a5d2f865@epcas1p1.samsung.com>
2016-10-18 10:39 ` Jeremy Kim
2016-10-18 10:51   ` Jaehoon Chung
2016-10-18 10:54     ` Jeremy Kim

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='0d4301d229fc$607a9770$216fc650$@samsung.com' \
    --to=jh4u.kim@samsung.com \
    --cc=jh80.chung@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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