All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@stericsson.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Lee Jones <lee.jones@linaro.org>,
	Stefan NILSSON9 <stefan.xk.nilsson@stericsson.com>
Subject: Re: [PATCH 1/4] mmc: mmci: Bugfix in pio read for small packets
Date: Fri, 14 Oct 2011 10:07:54 +0200	[thread overview]
Message-ID: <4E97EDDA.8090108@stericsson.com> (raw)
In-Reply-To: <20111013154803.GH21648@n2100.arm.linux.org.uk>

>>> So if they apply, they are independent AFAICT.
>> 7108/1 and 7109/1, have real dependencies. Otherwise there none.
> 
> Ok, I assume that those depend on the first two patches.
> 
> So, I tried applying 7110/1 .. 7112/1 but the first rejects because it
> doesn't have the non-power-of-2 support patch applied (7107/1).  And
> it seems sensible that 7107/1 depends on 7106/1 (the PIO patch) which
> I believe to be a problem.
> 

I see the problem.

The patches from the patch serie "Clarify code paths for how to modify 
the power register" are independent from this "SDIO serie". Although the 
patches has been based upon the patches from the SDIO serie, which is as 
you say the reason to why they not apply cleanly.

I will upload a second version of the serie "Clarify code paths for how 
to modify the power register" which is NOT based on the "SDIO serie". 
Then when can discuss each serie separately.

> Therefore, I don't think any of these can be applied without the
> initial PIO patch.
> 
> One thing I haven't yet mentioned is about the non-power-of-2 support -
> surely this can only be supported if blksz_datactrl16 is set?  If so,
> shouldn't it key off that?  I don't see how it could otherwise support
> non-power of 2 block sizes with just a log2 of the block size programmed
> into the data control register.
> 

Your observation is correct, but at the same time do we really need to 
have such a dependency check in the code? The hardware setup is handled 
in the variant struct completely, so we believe that should be enough.








WARNING: multiple messages have this Message-ID (diff)
From: ulf.hansson@stericsson.com (Ulf Hansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] mmc: mmci: Bugfix in pio read for small packets
Date: Fri, 14 Oct 2011 10:07:54 +0200	[thread overview]
Message-ID: <4E97EDDA.8090108@stericsson.com> (raw)
In-Reply-To: <20111013154803.GH21648@n2100.arm.linux.org.uk>

>>> So if they apply, they are independent AFAICT.
>> 7108/1 and 7109/1, have real dependencies. Otherwise there none.
> 
> Ok, I assume that those depend on the first two patches.
> 
> So, I tried applying 7110/1 .. 7112/1 but the first rejects because it
> doesn't have the non-power-of-2 support patch applied (7107/1).  And
> it seems sensible that 7107/1 depends on 7106/1 (the PIO patch) which
> I believe to be a problem.
> 

I see the problem.

The patches from the patch serie "Clarify code paths for how to modify 
the power register" are independent from this "SDIO serie". Although the 
patches has been based upon the patches from the SDIO serie, which is as 
you say the reason to why they not apply cleanly.

I will upload a second version of the serie "Clarify code paths for how 
to modify the power register" which is NOT based on the "SDIO serie". 
Then when can discuss each serie separately.

> Therefore, I don't think any of these can be applied without the
> initial PIO patch.
> 
> One thing I haven't yet mentioned is about the non-power-of-2 support -
> surely this can only be supported if blksz_datactrl16 is set?  If so,
> shouldn't it key off that?  I don't see how it could otherwise support
> non-power of 2 block sizes with just a log2 of the block size programmed
> into the data control register.
> 

Your observation is correct, but at the same time do we really need to 
have such a dependency check in the code? The hardware setup is handled 
in the variant struct completely, so we believe that should be enough.

  reply	other threads:[~2011-10-14  8:08 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  7:46 [PATCH 1/4] mmc: mmci: Bugfix in pio read for small packets Ulf Hansson
2011-09-27  7:46 ` Ulf Hansson
2011-10-01 16:09 ` Russell King - ARM Linux
2011-10-01 16:09   ` Russell King - ARM Linux
2011-10-03  7:08   ` Stefan Nilsson XK
2011-10-03  7:08     ` Stefan Nilsson XK
2011-10-07 13:38     ` Ulf Hansson
2011-10-07 13:38       ` Ulf Hansson
2011-10-07 19:11       ` Russell King - ARM Linux
2011-10-07 19:11         ` Russell King - ARM Linux
2011-10-14  7:38         ` Stefan Nilsson XK
2011-10-14  7:38           ` Stefan Nilsson XK
2011-10-07 13:45   ` Ulf Hansson
2011-10-07 13:45     ` Ulf Hansson
2011-10-08  9:10     ` Russell King - ARM Linux
2011-10-08  9:10       ` Russell King - ARM Linux
2011-10-09  6:59       ` Linus Walleij
2011-10-09  6:59         ` Linus Walleij
2011-10-10  8:23         ` Ulf Hansson
2011-10-10  8:23           ` Ulf Hansson
2011-10-13 15:48           ` Russell King - ARM Linux
2011-10-13 15:48             ` Russell King - ARM Linux
2011-10-14  8:07             ` Ulf Hansson [this message]
2011-10-14  8:07               ` Ulf Hansson

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=4E97EDDA.8090108@stericsson.com \
    --to=ulf.hansson@stericsson.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=stefan.xk.nilsson@stericsson.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.