All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 1/2] drivers; add DM_NO_OF Kconfig option
Date: Sun, 27 May 2018 19:45:12 -0600	[thread overview]
Message-ID: <CAPnjgZ2dACRFV0dmC_0omOaHVbR5f-X_rVpt9zdwaO85tnKokg@mail.gmail.com> (raw)
In-Reply-To: <20180527072233.GB17528@jerusalem>

+Tom

Hi Angelo,

On 27 May 2018 at 01:22, Angelo Dureghello <angelo@sysam.it> wrote:
> Hi Simon,
>
> On Sat, May 26, 2018 at 04:18:57PM -0600, Simon Glass wrote:
>> Hi Angelo,
>>
>> On 3 May 2018 at 16:01, Angelo Dureghello <angelo@sysam.it> wrote:
>> > To be able to build spi driver with DM support, a new config
>> > option has been introduced (DM_NO_OF) since m68k architecture
>> > does not support fdt.
>> >
>> > ---
>> > Changes from v1:
>> > - split into 2 patches
>> >
>> > Signed-off-by: Angelo Dureghello <angelo@sysam.it>
>> > ---
>> >  arch/Kconfig             |  1 +
>> >  drivers/core/Kconfig     |  4 ++++
>> >  drivers/spi/spi-uclass.c | 12 +++++++-----
>> >  3 files changed, 12 insertions(+), 5 deletions(-)
>> >
>>
>> Is it possible to use SPL_OF_PLATDATA instead?
>>
> I have seen that setting, but my understanding is that
> SPL_OF_PLATDATA ws made for a different purpose, and also, i
> tried to use it, but cannot select it from menuconfig.
>
>> How come m68k cannot use device tree?
>>
> There was never any devicetree implementation, probably becouse it
> is missing on Linux too.

It is a real shame that we can't do better than that.

I've added Tom in for comment as I'm not sure what is best here.

Regards,
Simon

  reply	other threads:[~2018-05-28  1:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03 22:01 [U-Boot] [PATCH v2 1/2] drivers; add DM_NO_OF Kconfig option Angelo Dureghello
2018-05-26 22:18 ` Simon Glass
2018-05-27  7:22   ` Angelo Dureghello
2018-05-28  1:45     ` Simon Glass [this message]
2018-05-29  0:59       ` Tom Rini
2018-05-29  8:20         ` Angelo Dureghello
2018-05-30 19:58         ` Angelo Dureghello
2018-05-31 13:01           ` Simon Glass
2018-06-01  1:51           ` Tom Rini

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=CAPnjgZ2dACRFV0dmC_0omOaHVbR5f-X_rVpt9zdwaO85tnKokg@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.