All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] arm: socfpga: Enable DM for Cadence and DW SPI
Date: Thu, 19 Feb 2015 10:44:54 +0100	[thread overview]
Message-ID: <201502191044.54996.marex@denx.de> (raw)
In-Reply-To: <CAPnjgZ0n6GisrR7rhazaNiOGq15s3BdRJm3Kd8sT5u4gMQEtNQ@mail.gmail.com>

On Thursday, February 19, 2015 at 02:07:13 AM, Simon Glass wrote:
> Hi Marek,
> 
> On 18 February 2015 at 14:36, Marek Vasut <marex@denx.de> wrote:
> > Enable DM in case these two drivers are enabled, since these
> > two drivers depend on DM.
> > 
> > Signed-off-by: Marek Vasut <marex@denx.de>
> > Cc: Simon Glass <sjg@chromium.org>
> > Cc: Stefan Roese <sr@denx.de>
> > Cc: Tom Rini <trini@ti.com>
> > ---
> > 
> >  include/configs/socfpga_common.h | 4 ++++
> >  1 file changed, 4 insertions(+)
> 
> This should use Kconfig now.

Hi,

there's still no Cadence SPI nor DW SPI controller entry in drivers/spi/Kconfig,
shall I add those then ?

Best regards,
Marek Vasut

  reply	other threads:[~2015-02-19  9:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-18 21:36 [U-Boot] [PATCH 1/2] dm: Protect device_unbind() with CONFIG_DM_DEVICE_REMOVE Marek Vasut
2015-02-18 21:36 ` [U-Boot] [PATCH 2/2] arm: socfpga: Enable DM for Cadence and DW SPI Marek Vasut
2015-02-19  1:07   ` Simon Glass
2015-02-19  9:44     ` Marek Vasut [this message]
2015-02-19 18:28       ` Simon Glass
2015-03-05 21:00         ` Marek Vasut
2015-02-19  1:06 ` [U-Boot] [PATCH 1/2] dm: Protect device_unbind() with CONFIG_DM_DEVICE_REMOVE Simon Glass
2015-02-19  8:50   ` Marek Vasut
2015-02-19 14:29     ` Simon Glass
2015-02-19 14:34       ` Marek Vasut
2015-02-19 15:24         ` Simon Glass
2015-02-19 18:19           ` Marek Vasut
2015-02-20 19:31             ` Simon Glass
2015-03-05 21:00               ` Marek Vasut
2015-02-19 18:27   ` Simon Glass

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=201502191044.54996.marex@denx.de \
    --to=marex@denx.de \
    --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.