All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Yann GAUTIER <yann.gautier@foss.st.com>
Cc: Marek Vasut <marex@denx.de>, Ulf Hansson <ulf.hansson@linaro.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [Linux-stm32] [PATCH] [RFC] mmc: mmci: Add support for probing bus voltage level translator
Date: Fri, 15 Jan 2021 23:49:54 +0100	[thread overview]
Message-ID: <CACRpkdY=n_-5giDVyqvSbCF7wy_-Xf7RfOrQbxrCQ+jC9b2rXw@mail.gmail.com> (raw)
In-Reply-To: <ad4a108e-81f1-daf5-9921-9884ed06d237@foss.st.com>

On Thu, Jan 14, 2021 at 11:13 AM Yann GAUTIER <yann.gautier@foss.st.com> wrote:
> On 1/13/21 3:45 PM, Marek Vasut wrote:
> > On 1/13/21 3:21 PM, Yann GAUTIER wrote:
> >> On 1/13/21 12:52 PM, Marek Vasut wrote:

> >> I also wonder if this HW detection should be done in kernel, or if it
> >> should be done in Bootloader. But it may be more complex, to add the
> >> st,use_ckin in kernel DT if bootloader detects this translator.
> >
> > Lets not attempt to hide inobvious functionality in bootloaders, the
> > kernel should be independent of bootloader where possible. And here it
> > is clearly and easily possible.
>
> OK for this part, I understand it will be better not to hide this in
> bootloader.

We all agree. I am against bootloaderism, the tendency to toss all
complex hardware detection over the wall and call it
a bootloader problem.

Let's proceed with Marek's solution.

Yours,
Linus Walleij

  reply	other threads:[~2021-01-15 22:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-05 14:07 [PATCH] [RFC] mmc: mmci: Add support for probing bus voltage level translator Marek Vasut
2021-01-13 10:44 ` Ulf Hansson
2021-01-13 11:34   ` Marek Vasut
2021-01-13 11:38     ` Ulf Hansson
2021-01-13 11:52       ` Marek Vasut
2021-01-13 14:21         ` [Linux-stm32] " Yann GAUTIER
2021-01-13 14:45           ` Marek Vasut
2021-01-14 10:13             ` Yann GAUTIER
2021-01-15 22:49               ` Linus Walleij [this message]
2021-01-15 22:48     ` Linus Walleij
2021-01-15 22:47 ` Linus Walleij

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='CACRpkdY=n_-5giDVyqvSbCF7wy_-Xf7RfOrQbxrCQ+jC9b2rXw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@denx.de \
    --cc=ulf.hansson@linaro.org \
    --cc=yann.gautier@foss.st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.