linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the arm-soc tree with Linus' tree
Date: Mon, 5 Sep 2016 19:26:03 +0100	[thread overview]
Message-ID: <20160905182603.GS1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <20160905105803.13ed27ff@canb.auug.org.au>

On Mon, Sep 05, 2016 at 10:58:03AM +1000, Stephen Rothwell wrote:
> I fixed it up (I deleted the file) and can carry the fix as
> necessary. This is now fixed as far as linux-next is concerned, but any
> non trivial conflicts should be mentioned to your upstream maintainer
> when your tree is submitted for merging.  You may also want to consider
> cooperating with the maintainer of the conflicting tree to minimise any
> particularly complex conflicts.

That's the "simple" way of making the conflict go away, but I'm afraid
it's really not that simple.

Having just looked at the SMC91x definition for realview, it shows that
the SMC91x binding, like many of the conversions that the patch in my
tree fixes, has been created without a proper understanding of the
hardware.  To put it simply, it is broken.

The binding only allows _one_ register width to be specified, which is
completely incorrect: the binding _must_ allow multiple register widths
to be specified.  This is what SMC91x has always expected: to be told
which register access widths it is permitted to make.

That must include at least one of 8 or 16 bit accesses, but 32-bit
access is optional.

The result will be that - despite I've fixed up all the static platform
data to be correct, there's no way to fix up the DT binding without
inventing a new one.

So, deleting the Realview (and other) board files results in platforms
that can't use networking - it's worse than that, because the smc91x
driver will BUG() as a result of this at boot time.

Since the patch in my tree is fixing a regression caused by the broken
conversions, I'm not mindful to drop it from the merge window - I
actually want to push it into -rc kernels.  We _do_ need to fix the
DT regressions, and quickly though, and push those with this patch.

Since I don't use the SMC91x with DT, that's outside of what I can
test, so consider this a call for help on that subject.

-- 
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-09-05 18:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  0:58 linux-next: manual merge of the arm-soc tree with Linus' tree Stephen Rothwell
2016-09-05 18:26 ` Russell King - ARM Linux [this message]
2016-09-06 10:17   ` Arnd Bergmann
2016-09-06 10:42     ` Russell King - ARM Linux
2016-09-25 16:07   ` Robert Jarzmik
  -- strict thread matches above, loose matches on Subject: below --
2022-05-27  0:39 Stephen Rothwell
2022-05-27 15:38 ` Hawkins, Nick
2022-05-28  0:29   ` Stephen Rothwell
2019-06-23 22:54 Stephen Rothwell
2018-10-28 23:14 Stephen Rothwell
2018-10-29 15:02 ` Tony Lindgren
2018-10-28 23:08 Stephen Rothwell
2016-01-20 22:40 Stephen Rothwell
2015-08-23 23:55 Stephen Rothwell
2015-06-01  0:25 Stephen Rothwell
2015-06-01  7:12 ` Michal Simek
2014-01-30  0:19 Stephen Rothwell
2014-01-30  5:33 ` Kevin Hilman
2014-01-30 21:47   ` Mike Turquette
2014-01-23  0:23 Stephen Rothwell
2013-08-27  8:29 Stephen Rothwell
2013-08-27 16:17 ` Stephen Warren
2013-08-28  0:06   ` Stephen Rothwell
2013-08-27  8:26 Stephen Rothwell
2013-07-08  4:03 Stephen Rothwell
2013-03-18  3:49 Stephen Rothwell
2012-10-04  4:33 Stephen Rothwell
2012-07-30  2:53 Stephen Rothwell
2012-03-15  6:50 Stephen Rothwell
2012-03-15  9:51 ` Laurent Pinchart
2012-03-15 20:01   ` Arnd Bergmann
2012-03-15 21:36     ` Rafael J. Wysocki
2012-03-08  6:07 Stephen Rothwell

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=20160905182603.GS1041@n2100.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=linux-arm-kernel@lists.infradead.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).