public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <ext-felipe.lima@nokia.com>
To: ext Dirk Behme <dirk.behme@googlemail.com>
Cc: Linux OMAP Mailing List <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH]: Fixing blksz_bits calling inside drivers/mmc/mmc.c and drivers/mmc/omap.c
Date: Fri, 27 Oct 2006 13:51:54 -0400	[thread overview]
Message-ID: <4542473A.4050709@nokia.com> (raw)
In-Reply-To: <454237BE.900@gmail.com>

ext Dirk Behme wrote:
> Felipe Balbi wrote:
>>>> Index: linux-omap/drivers/mmc/omap.c
>>>> ===================================================================
>>>> --- linux-omap.orig/drivers/mmc/omap.c    2006-10-27 
>>>> 09:18:34.000000000 -0400
>>>> +++ linux-omap/drivers/mmc/omap.c    2006-10-27 11:03:14.000000000 
>>>> -0400
>>>> @@ -633,10 +633,10 @@ mmc_omap_prepare_dma(struct mmc_omap_hos
>>>>      int sync_dev = 0;
>>>>  
>>>>      data_addr = host->phys_base + OMAP_MMC_REG_DATA;
>>>> -    frame = 1 << data->blksz_bits;
>>>> +    frame = 1 << data->blksz;
>>>>      count = sg_dma_len(sg);
>>>>  
>>>> -    if ((data->blocks == 1) && (count > (1 << data->blksz_bits)))
>>>> +    if ((data->blocks == 1) && (count > (1 << data->blksz)))
>>>>          count = frame;
>>>>  
>>>>      host->dma_len = count;
>>>> @@ -825,7 +825,7 @@ mmc_omap_prepare_data(struct mmc_omap_ho
>>>>      }
>>>>  
>>>>  
>>>> -    block_size = 1 << data->blksz_bits;
>>>> +    block_size = 1 << data->blksz;
>>>>  
>>>>      OMAP_MMC_WRITE(host, NBLK, data->blocks - 1);
>>>>      OMAP_MMC_WRITE(host, BLEN, block_size - 1);
>>>>
>>>> --- linux-omap/drivers/mmc/mmc.c    2006-10-26 06:42:31.000000000 
>>>> -0400
>>>> +++ linux-omap-dev/drivers/mmc/mmc.c    2006-10-26 
>>>> 09:53:24.000000000 -0400
>>>> @@ -996,7 +996,7 @@
>>>>  
>>>>          mmc_set_data_timeout(&data, card, 0);
>>>>  
>>>> -        data.blksz = 1 << 3;
>>>> +        data.blksz_bits = 1 << 3;
>>>>          data.blocks = 1;
>>>>          data.flags = MMC_DATA_READ;
>>>>          data.sg = &sg;
>>>
>>>
>>> This doesn't look correct to me (and compilation still
>>> fails). Why do you add data.blksz_bits in mmc.c again? It
>>> was removed by RMK at
>>>
>>> http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=blobdiff;h=5b9caa7978d34311839840243e38921255f6da4b;hp=74eaaee66de0e59532ba5655fddac5aaeea5ba08;hb=132919ba80ad207755fe271277bfefff865a54fe;f=drivers/mmc/mmc.c 
>>>
>>>
>>> Whats about the attachment instead? It additionally
>>> removes warning
>>>
>>> drivers/mmc/omap.c:587: warning: 'mmc_omap_switch_callback'
>>> defined but not used
>>>
>>> too.
>>>
>>> Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> Index: linux-osk/drivers/mmc/omap.c
>>> ===================================================================
>>> --- linux-osk.orig/drivers/mmc/omap.c
>>> +++ linux-osk/drivers/mmc/omap.c
>>> @@ -581,12 +581,6 @@ static void mmc_omap_switch_timer(unsign
>>>      schedule_work(&host->switch_work);
>>>  }
>>>  
>>> -/* FIXME: Handle card insertion and removal properly. Maybe use a mask
>>> - * for MMC state? */
>>> -static void mmc_omap_switch_callback(unsigned long data, u8 mmc_mask)
>>> -{
>>> -}
>>> -
>>>  static void mmc_omap_switch_handler(void *data)
>>>  {
>>>      struct mmc_omap_host *host = (struct mmc_omap_host *) data;
>>> @@ -633,10 +627,10 @@ mmc_omap_prepare_dma(struct mmc_omap_hos
>>>      int sync_dev = 0;
>>>  
>>>      data_addr = host->phys_base + OMAP_MMC_REG_DATA;
>>> -    frame = 1 << data->blksz_bits;
>>> +    frame = data->blksz;
>>>      count = sg_dma_len(sg);
>>>  
>>> -    if ((data->blocks == 1) && (count > (1 << data->blksz_bits)))
>>> +    if ((data->blocks == 1) && (count > (data->blksz)))
>>>          count = frame;
>>>  
>>>      host->dma_len = count;
>>> @@ -825,7 +819,7 @@ mmc_omap_prepare_data(struct mmc_omap_ho
>>>      }
>>>  
>>>  
>>> -    block_size = 1 << data->blksz_bits;
>>> +    block_size = data->blksz;
>>>  
>>>      OMAP_MMC_WRITE(host, NBLK, data->blocks - 1);
>>>      OMAP_MMC_WRITE(host, BLEN, block_size - 1);
>>>
>>>
>>>   
>>
>> But then you will need to modify the struct mmc_data...
>
> Mmh, why? Above patch compiles for me.
>
> blksz is part of the global struct mmc_data, isn't it?
>
> http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commitdiff;h=132919ba80ad207755fe271277bfefff865a54fe 
>
>
> http://source.mvista.com/git/gitweb.cgi?p=linux-omap-2.6.git;a=commit;h=132919ba80ad207755fe271277bfefff865a54fe 
>
>
> Do we both talk about recent git? Or do you use an other or locally 
> modified version?
>
> Best regards
>
> Dirk
>
Yep, my git tree is the newest version...
And I made a mistake here...

--- linux-omap/drivers/mmc/mmc.c    2006-10-26 06:42:31.000000000 -0400
+++ linux-omap-dev/drivers/mmc/mmc.c    2006-10-26 09:53:24.000000000 -0400
@@ -996,7 +996,7 @@
 
         mmc_set_data_timeout(&data, card, 0);
 
-        data.blksz = 1 << 3;
+        data.blksz_bits = 1 << 3;
         data.blocks = 1;
         data.flags = MMC_DATA_READ;
         data.sg = &sg;

It's deordered... it should appear like:

--- linux-omap/drivers/mmc/mmc.c    2006-10-26 06:42:31.000000000 -0400
+++ linux-omap-dev/drivers/mmc/mmc.c    2006-10-26 09:53:24.000000000 -0400
@@ -996,7 +996,7 @@
 
         mmc_set_data_timeout(&data, card, 0);
 
-        data.blksz_bits = 1 << 3;
+        data.blksz = 1 << 3;
         data.blocks = 1;
         data.flags = MMC_DATA_READ;
         data.sg = &sg;

-- 
Best Regards,

Felipe Balbi
ext-felipe.lima@nokia.com
OSMRC

  reply	other threads:[~2006-10-27 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 15:13 [PATCH]: Fixing blksz_bits calling inside drivers/mmc/mmc.c and drivers/mmc/omap.c Felipe Balbi
2006-10-27 16:02 ` Dirk Behme
2006-10-27 16:20   ` Felipe Balbi
2006-10-27 16:30     ` Felipe Balbi
2006-10-27 16:45     ` Dirk Behme
2006-10-27 17:51       ` Felipe Balbi [this message]
2006-10-27 18:21         ` Dirk Behme

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=4542473A.4050709@nokia.com \
    --to=ext-felipe.lima@nokia.com \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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