From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Barry Song <baohua@kernel.org>,
Anton Vorontsov <anton@enomsg.org>,
Stephen Warren <swarren@wwwdotorg.org>,
spear-devel@list.st.com, linux-mmc <linux-mmc@vger.kernel.org>,
Chris Ball <chris@printf.net>,
Michal Simek <michal.simek@xilinx.com>,
Thierry Reding <thierry.reding@gmail.com>,
Viresh Kumar <viresh.linux@gmail.com>,
Ben Dooks <ben-linux@fluff.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
linuxppc-dev@lists.ozlabs.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 23/38] mmc: sdhci: convert sdhci_set_uhs_signaling() into a library function
Date: Wed, 18 Jun 2014 00:42:26 +0100 [thread overview]
Message-ID: <20140617234226.GP23430@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPDyKFrp8JokqBbo3rg2i6WYykU1C9CuPF0FL7AOHh=Gcp5=hg@mail.gmail.com>
On Mon, Jun 16, 2014 at 02:17:30PM +0200, Ulf Hansson wrote:
> On 16 June 2014 12:46, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> > On Wed, Apr 23, 2014 at 08:08:07PM +0100, Russell King wrote:
> >> @@ -1507,25 +1529,7 @@ static void sdhci_do_set_ios(struct sdhci_host *host, struct mmc_ios *ios)
> >> host->ops->set_clock(host, host->clock);
> >> }
> >>
> >> - if (host->ops->set_uhs_signaling)
> >> - host->ops->set_uhs_signaling(host, ios->timing);
> >> - else {
> >> - ctrl_2 = sdhci_readw(host, SDHCI_HOST_CONTROL2);
> >> - /* Select Bus Speed Mode for host */
> >> - ctrl_2 &= ~SDHCI_CTRL_UHS_MASK;
> >> - if ((ios->timing == MMC_TIMING_MMC_HS200) ||
> >> - (ios->timing == MMC_TIMING_UHS_SDR104))
> >> - ctrl_2 |= SDHCI_CTRL_UHS_SDR104;
> >> - else if (ios->timing == MMC_TIMING_UHS_SDR12)
> >> - ctrl_2 |= SDHCI_CTRL_UHS_SDR12;
> >> - else if (ios->timing == MMC_TIMING_UHS_SDR25)
> >> - ctrl_2 |= SDHCI_CTRL_UHS_SDR25;
> >> - else if (ios->timing == MMC_TIMING_UHS_SDR50)
> >> - ctrl_2 |= SDHCI_CTRL_UHS_SDR50;
> >> - else if (ios->timing == MMC_TIMING_UHS_DDR50)
> >> - ctrl_2 |= SDHCI_CTRL_UHS_DDR50;
> >> - sdhci_writew(host, ctrl_2, SDHCI_HOST_CONTROL2);
> >> - }
> >> + host->ops->set_uhs_signaling(host, ios->timing);
> >>
> >> if (!(host->quirks2 & SDHCI_QUIRK2_PRESET_VALUE_BROKEN) &&
> >> ((ios->timing == MMC_TIMING_UHS_SDR12) ||
> >
> > Whoever decided to poorly pick these patches up against my will has
> > slightly messed this patch up - whereas my original patch left the
> > code correctly formatted, when whoever applied this patch did so, they
> > left an additional blank line in the above.
>
> Hi Russell,
>
> We kindly pinged you several times asking for your state and for the
> PR, but I suppose you were just too busy. Your PR were kind of
> blocking patches for sdhci, if you remember.
I wasn't "too busy". I had walked away from all kernel maintanence in
disgust at the way many in the ARM community ignores questions, and
ignores patches which need testing - I'm talking there about the L2C
patch series which was extremely poorly tested, and still, to this day,
has questions outstanding. Yes, the code now produces warnings. It
produces warnings /because/ people were not willing to help.
Those warnings serve as a reminder that there's still problems which
need solving there, and they're not going to go away until those
problems are solved.
While I don't like pushing unfinished code into mainline, in this case,
others deemed the patch set too important _not_ to go into mainline
even with these problems.
Now, it's been /soo/ long since I worked on that patch set that my
knowledge has now diminished... so it's now going to be _much_ harder
to resolve those issues than it would have been three months ago.
And I'm also holding a grudge, and I bear grudges for a long time, so
expect me to be "difficult" towards Linux stuff for a while yet.
> The mmc people were also very helping in sending patches to fixup
> related regressions, immediately after we merged your patchset. Thus
> together I think we managed to pull it off.
The formatting problem I refer to above is line 1532/1533 in sdhci.c -
there's an additional blank line which somehow got left behind, caused
presumably by insufficient attention paid to cleaning up a conflict
between my original patches and the state of the tree they were
applied to.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-06-17 23:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 18:55 [PATCH 00/38] MMC updates, plus CuBox-i WiFi support Russell King - ARM Linux
2014-04-23 19:06 ` [PATCH 09/38] mmc: sdhci: convert generic bus width setup to library function Russell King
2014-04-23 19:07 ` [PATCH 10/38] mmc: sdhci: convert reset into a " Russell King
2014-04-23 19:07 ` [PATCH 17/38] mmc: sdhci: convert sdhci_set_clock() " Russell King
2014-04-23 19:08 ` [PATCH 23/38] mmc: sdhci: convert sdhci_set_uhs_signaling() " Russell King
2014-06-16 10:46 ` Russell King - ARM Linux
2014-06-16 12:17 ` Ulf Hansson
2014-06-16 16:10 ` Ulf Hansson
2014-06-17 23:42 ` Russell King - ARM Linux [this message]
2014-06-19 12:28 ` Russell King - ARM Linux
2014-06-19 15:57 ` Stephen Warren
2014-06-19 17:02 ` Olof Johansson
2014-04-24 8:25 ` [PATCH 00/38] MMC updates, plus CuBox-i WiFi support Ulf Hansson
2014-04-24 10:17 ` Russell King - ARM Linux
2014-04-24 10:52 ` Ulf Hansson
2014-04-24 10:57 ` Russell King - ARM Linux
2014-04-24 11:13 ` Ulf Hansson
2014-04-25 9:03 ` Russell King - ARM Linux
2014-04-25 11:18 ` Ulf Hansson
2014-04-25 11:20 ` Russell King - ARM Linux
2014-04-25 11:40 ` Ulf Hansson
2014-04-28 16:42 ` Stephen Warren
2014-04-28 16:52 ` Chris Ball
2014-05-07 20:49 ` Tim Kryger
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=20140617234226.GP23430@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=anton@enomsg.org \
--cc=baohua@kernel.org \
--cc=ben-linux@fluff.org \
--cc=chris@printf.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michal.simek@xilinx.com \
--cc=spear-devel@list.st.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=viresh.linux@gmail.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;
as well as URLs for NNTP newsgroup(s).