mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Olof Johansson <olof@lixom.net>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Linus <torvalds@linux-foundation.org>,
	linux-mmc <linux-mmc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"arm@kernel.org" <arm@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [GIT PULL] MMC fixes for v.4.12 rc3 - take 2/2
Date: Fri, 2 Jun 2017 12:13:18 +0200	[thread overview]
Message-ID: <bbdcdf34-4c05-b37a-5e7d-02d8a12d072d@linaro.org> (raw)
In-Reply-To: <20170602000522.GH13314@localhost>

On 02/06/2017 02:05, Olof Johansson wrote:

[ ... ]

>> For the story, this mmc/sdio is for the WiFi and this one was working for some
>> version of the bootloader which initialized the clock and set the enable line
>> for the chip. That is bad because the WiFi is working as a side effect from the
>> boot loader.
>>
>> In order to properly make support for the WiFi in the kernel, we need to sort
>> out this by:
>>
>>  - Reset the mmc
>>  - Implement the clock at the pmic level
>>  - Add the mfd clock cell
>>  - Add the DT definition
> 
> Ok, that's all fine but it's not really what we would call a fix. Hardware
> bringup and enabling of major drivers is usually done through the release
> cycle and merged in the merge window, not as "fixes" after it's closed.

Yes, I second you on that. That is the reason why I was not really
convinced about this series for -rc.

> It's not causing problems in this case, but if it happens often it runs
> the risk of causing a mess due to conflicting contributions from different
> subsystem maintainers (i.e. in particular the DT contents updates),
> and in general circumvents the development model we're keeping where
> things are tested in -next before merge, etc.
> 
> Anyway, water under the bridge but it's stuff to think about for next time
> around.

Copy that. Thanks!

  -- Daniel


-- 
 <http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2017-06-02 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-26 13:08 Ulf Hansson
2017-05-26 16:24 ` Olof Johansson
2017-05-28 10:26   ` Ulf Hansson
2017-05-29 10:22     ` Daniel Lezcano
2017-06-02  0:05       ` Olof Johansson
2017-06-02 10:13         ` Daniel Lezcano [this message]

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=bbdcdf34-4c05-b37a-5e7d-02d8a12d072d@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=olof@lixom.net \
    --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

all inboxes | Powered by JetHome®