public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] Kconfig: Add entry for VF610 NAND NFC device tree aware driver
Date: Mon, 3 Dec 2018 15:36:05 +0100	[thread overview]
Message-ID: <20181203153605.2e0de6cf@jawa> (raw)
In-Reply-To: <f6b559dad5e821dd912b1ee5a63de62d@agner.ch>

Hi Stefan,

> On 03.12.2018 10:24, Lukasz Majewski wrote:
> > This commit provides code to add proper entry to Kconfig to enable
> > support for VF610 device tree aware driver.  
> 
> Looks like a start, 

Indeed - this is a start. Vybrid is a bit behind the current u-boot
peace of development.

I'm trying to give it some momentum.

> but ideally we should also move all the
> board/system specific properties to device-tree (e.g.
> CONFIG_SYS_NAND_VF610_NFC_45_ECC_BYTES).

Yes, that would be a long term goal. However, those configs are already
moved to Kconfig, so there is no urgent need to make the conversion
now.

> 
> --
> Stefan
> 
> > 
> > Signed-off-by: Lukasz Majewski <lukma@denx.de>
> > 
> > ---
> > 
> >  drivers/mtd/nand/raw/Kconfig | 11 +++++++++++
> >  1 file changed, 11 insertions(+)
> > 
> > diff --git a/drivers/mtd/nand/raw/Kconfig
> > b/drivers/mtd/nand/raw/Kconfig index 008f7b4b4b..fd1723feda 100644
> > --- a/drivers/mtd/nand/raw/Kconfig
> > +++ b/drivers/mtd/nand/raw/Kconfig
> > @@ -88,6 +88,15 @@ config NAND_VF610_NFC
> >  	  The driver supports a maximum 2k page size. The driver
> >  	  currently does not support hardware ECC.
> >  
> > +if NAND_VF610_NFC
> > +
> > +config NAND_VF610_NFC_DT
> > +        bool "Support Vybrid's vf610 NAND controller as a DT
> > device"
> > +        depends on OF_CONTROL && MTD
> > +        help
> > +          Enable the driver for Vybrid's vf610 NAND flash on
> > platforms
> > +	  using device tree.
> > +
> >  choice
> >  	prompt "Hardware ECC strength"
> >  	depends on NAND_VF610_NFC
> > @@ -103,6 +112,8 @@ config SYS_NAND_VF610_NFC_60_ECC_BYTES
> >  
> >  endchoice
> >  
> > +endif
> > +
> >  config NAND_PXA3XX
> >  	bool "Support for NAND on PXA3xx and Armada 370/XP/38x"
> >  	select SYS_NAND_SELF_INIT  




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20181203/e687526e/attachment.sig>

      reply	other threads:[~2018-12-03 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-03  9:24 [U-Boot] [PATCH 1/2] Kconfig: Add entry for VF610 NAND NFC device tree aware driver Lukasz Majewski
2018-12-03  9:24 ` [U-Boot] [PATCH 2/2] nand: vybrid: Extend the vf610 NFC NAND driver to support device tree (and DM) Lukasz Majewski
2018-12-03 14:03 ` [U-Boot] [PATCH 1/2] Kconfig: Add entry for VF610 NAND NFC device tree aware driver Stefan Agner
2018-12-03 14:36   ` Lukasz Majewski [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=20181203153605.2e0de6cf@jawa \
    --to=lukma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox