linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Doug Anderson <dianders@chromium.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SoC Team <soc@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: SoC fixes for v5.10, part 3
Date: Mon, 30 Nov 2020 22:54:59 +0000	[thread overview]
Message-ID: <20201130225459.GB1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAHk-=wi2CQwAnKucLwE8vNZgXxyRy6L+DcgjGqxKHwbacKgaMQ@mail.gmail.com>

On Mon, Nov 30, 2020 at 10:22:58AM -0800, Linus Torvalds wrote:
> > I guess the question is: why is static assignment of numbers not an
> > acceptable solution to the problem?  It gives us the desired fixed
> > numbers and automatically avoids all weird probe ordering / dependency
> > problems.
> 
> I think that if this had been done originally, it would probably be fine.

It was not done originally, because the original structure of the MMC
bus was:

host controller ---+--- card 1
                   +--- card 2
		   +--- card 3
		   ...

So one host controller could be connected to multiple different cards,
and the bus has a way to detect each card individually. This means we
had no idea how many cards would be connected to any one controller,
and it was entirely sensible to allocate MMC block devices in the order
we discovered the cards.

The SD specification, this became limited to just one card per
controller to allow for faster speeds.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-11-30 22:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 20:51 [GIT PULL] ARM: SoC fixes for v5.10, part 3 Arnd Bergmann
2020-11-27 22:56 ` Linus Torvalds
2020-11-30 17:04   ` Doug Anderson
2020-11-30 17:44     ` Linus Torvalds
2020-11-30 18:05       ` Russell King - ARM Linux admin
2020-11-30 18:15         ` Linus Torvalds
2020-11-30 19:06           ` Russell King - ARM Linux admin
2020-11-30 18:11       ` Doug Anderson
2020-11-30 18:22         ` Linus Torvalds
2020-11-30 22:54           ` Russell King - ARM Linux admin [this message]
2020-12-01 11:39           ` Ulf Hansson
2020-12-01 14:00             ` Arnd Bergmann
2020-12-07 20:19               ` Geert Uytterhoeven
2020-12-07 21:55                 ` Arnd Bergmann
2020-12-07 22:15                   ` Doug Anderson
2020-12-08  7:31                     ` Geert Uytterhoeven
2020-12-14 20:22                       ` Ulf Hansson
2020-12-15  8:19                         ` Geert Uytterhoeven
2020-12-15  9:53                           ` Ulf Hansson
2020-11-30 17:27   ` Dmitry Torokhov
2020-12-05 20:48     ` Pavel Machek
2020-11-27 23:29 ` pr-tracker-bot

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=20201130225459.GB1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=arnd@kernel.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soc@kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).