mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	Tushar Behera <tushar.behera@linaro.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	linux-samsung-soc@vger.kernel.org, jslaby@suse.cz,
	ben.dooks@codethink.co.uk, broonie@kernel.org
Subject: Re: [PATCH 2/2] serial: pl011: Move uart_register_driver call to device probe
Date: Mon, 17 Feb 2014 15:35:18 +0000	[thread overview]
Message-ID: <20140217153518.30891455@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140214003834.GH30257@n2100.arm.linux.org.uk>

> > How?  What two different busses will see this same device?  The amba bus
> > code should prevent that from happening, right?  If not, there's bigger
> > problems in that bus code :)
> 
> Where is that requirement documented?  It isn't documented.  No one
> implements any kind of locking at the bus level to prevent this, not
> PCI, nor platform devices.

We don't want bus locking. There are lots of busses that can be parallel
probed and in some cases its expensive not to do so. We may well need to
do much more parallel probing in PCI bus in future and we may be parallel
probing multiple bus types at once.

The uart_register hack is simply broken. Nobody can stop you merging it
Greg but in the long term its the wrong approach.

We've identified a correct working approach which is to simply add a
CONFIG entry to the ARM tree and a few ifdefs to the problem drivers to
make the "problem" (in fact a complete fictional non-problem) go away and
to get rid of the mess over time completely as the drivers are set
dynamic and it turns out that all the userspace happens to already handle
this just fine.

Far better than botchfixes to uart registration code that will haunt us
for years.

Alan

  reply	other threads:[~2014-02-17 15:35 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  9:02 [PATCH 0/2] serial: " Tushar Behera
2014-01-20  9:02 ` [PATCH 1/2] serial: samsung: " Tushar Behera
2014-01-20 10:05   ` Russell King - ARM Linux
2014-01-20 11:53     ` Tushar Behera
2014-01-20 12:26       ` Russell King - ARM Linux
2014-01-20 21:43       ` Alan Cox
2014-01-20 23:14         ` Mark Brown
2014-01-20 23:21           ` Russell King - ARM Linux
2014-01-20 23:35             ` Alan Cox
2014-01-20 23:52               ` Greg Kroah-Hartman
2014-01-20 23:47           ` Alan Cox
2014-01-21  0:16             ` Russell King - ARM Linux
2014-01-21  9:03               ` Alan Cox
2014-01-21  9:49                 ` Russell King - ARM Linux
     [not found]               ` <50b66ac6-1150-4ad7-aeaf-3d0dce77334d@email.android.com>
2014-01-26 11:54                 ` Russell King - ARM Linux
2014-01-27  4:30                   ` Nicolas Pitre
2014-01-27 10:07                     ` Alan Cox
2014-01-27 12:32                     ` Russell King - ARM Linux
2014-01-27 15:03                       ` Nicolas Pitre
2014-01-21 16:59             ` Mark Brown
2014-01-21 18:30               ` Russell King - ARM Linux
2014-01-23 18:04       ` Alan Cox
2014-01-23 18:40         ` Mark Brown
2014-01-23 18:47           ` Tomasz Figa
2014-01-23 19:36             ` Mark Brown
2014-01-23 19:51               ` Alan Cox
2014-01-23 20:05                 ` Mark Brown
2014-01-23 21:33                   ` Alan Cox
2014-01-24 12:03                     ` Mark Brown
2014-01-24 14:38                       ` Alan Cox
2014-01-27  0:15                         ` Mark Brown
2014-01-26 21:09               ` Pavel Machek
2014-01-27  0:04                 ` Alan Cox
2014-01-20 21:16     ` Greg KH
2014-01-20 21:32       ` Russell King - ARM Linux
2014-01-20 23:11         ` Greg KH
2014-01-20 23:16           ` Russell King - ARM Linux
2014-01-20 23:51             ` Greg KH
2014-01-21  0:07               ` Russell King - ARM Linux
2014-01-21  0:26                 ` Greg KH
2014-01-21  0:38                   ` Russell King - ARM Linux
2014-01-21  9:25                     ` One Thousand Gnomes
2014-01-21  9:45                       ` Russell King - ARM Linux
2014-01-20  9:02 ` [PATCH 2/2] serial: pl011: " Tushar Behera
2014-01-20 10:04   ` Russell King - ARM Linux
2014-02-13 18:12     ` Greg KH
2014-02-13 18:15       ` Russell King - ARM Linux
2014-02-13 18:27         ` Greg KH
2014-02-13 18:42           ` Russell King - ARM Linux
2014-02-13 23:26             ` Greg KH
2014-02-14  0:07               ` Russell King - ARM Linux
2014-02-14  0:14                 ` Greg KH
2014-02-14  0:38                   ` Russell King - ARM Linux
2014-02-17 15:35                     ` One Thousand Gnomes [this message]
2014-02-17 15:54                       ` One Thousand Gnomes
2014-02-17 23:50                       ` Mark Brown
2014-02-18 10:09                         ` Etched Pixels
2014-02-19 13:57                           ` Mark Brown
2014-02-19 14:47                             ` One Thousand Gnomes
2014-02-19 15:53                               ` Mark Brown
2014-02-19  0:47                   ` One Thousand Gnomes

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=20140217153518.30891455@alan.etchedpixels.co.uk \
    --to=gnomes@lxorguk.ukuu.org.uk \
    --cc=ben.dooks@codethink.co.uk \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tushar.behera@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

all inboxes | Powered by JetHome®