public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: <Eugen.Hristev@microchip.com>
To: <Durai.ManickamKR@microchip.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCHv3 0/3] Add support for sam9x60_curiosity
Date: Wed, 27 Apr 2022 06:00:02 +0000	[thread overview]
Message-ID: <ebadbbbc-d612-b2a6-3667-31990ff22aee@microchip.com> (raw)
In-Reply-To: <20220404055320.26362-1-durai.manickamkr@microchip.com>

On 4/4/22 8:53 AM, Durai Manickam KR wrote:
> ---
> v2 -> v3:
> - Few symbols defined in the board specific header file (i.e)
>    sam9x60_curiosity.h are no longer accepted by the u-boot mainline. So the
>    below changes has been done.
> - NAND symbols are no longer accepted by the u-boot mainline. This shall be
>    migrated to device tree model. So, this patch series contains only SDMMC
>    support. NAND support will be added once device tree model is implemented.
> - Removed sam9x60_curiosity_nand_hw_init function from the board specific C file.
> - Removed the NAND config support in the SDMMC defconfig.
> - Converted CONFIG_BOOTP_BOOTFILESIZE to Kconfig
> 
> ---
> v1 -> v2:
> - This patch series adds support for sam9x60_curiosity.
> - Converted CONFIG_ATMEL_LEGACY to Kconfig. Previosly sent patch series from
>    u-boot/master branch now sending the patch series on top of u-boot/next branch
>    as v2.
> 
> Durai Manickam KR (3):
>    board: Add sam9x60_curiosity support
>    ARM: dts: Add device tree files for sam9x60_curiosity
>    configs: Add sam9x60_curiosity_mmc_defconfig
> 
>   arch/arm/dts/Makefile                         |  2 +
>   .../dts/at91-sam9x60_curiosity-u-boot.dtsi    | 79 +++++++++++++++++++
>   arch/arm/dts/at91-sam9x60_curiosity.dts       | 74 +++++++++++++++++
>   arch/arm/mach-at91/Kconfig                    |  7 ++
>   board/atmel/sam9x60_curiosity/Kconfig         | 15 ++++
>   board/atmel/sam9x60_curiosity/MAINTAINERS     |  7 ++
>   board/atmel/sam9x60_curiosity/Makefile        |  7 ++
>   .../sam9x60_curiosity/sam9x60_curiosity.c     | 75 ++++++++++++++++++
>   configs/sam9x60_curiosity_mmc_defconfig       | 74 +++++++++++++++++
>   include/configs/sam9x60_curiosity.h           | 31 ++++++++
>   10 files changed, 371 insertions(+)
>   create mode 100644 arch/arm/dts/at91-sam9x60_curiosity-u-boot.dtsi
>   create mode 100644 arch/arm/dts/at91-sam9x60_curiosity.dts
>   create mode 100644 board/atmel/sam9x60_curiosity/Kconfig
>   create mode 100644 board/atmel/sam9x60_curiosity/MAINTAINERS
>   create mode 100644 board/atmel/sam9x60_curiosity/Makefile
>   create mode 100644 board/atmel/sam9x60_curiosity/sam9x60_curiosity.c
>   create mode 100644 configs/sam9x60_curiosity_mmc_defconfig
>   create mode 100644 include/configs/sam9x60_curiosity.h
> 
> --
> 2.25.1
> 

Applied to u-boot-at91/master , thanks !

      parent reply	other threads:[~2022-04-27  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  5:53 [PATCHv3 0/3] Add support for sam9x60_curiosity Durai Manickam KR
2022-04-04  5:53 ` [PATCHv3 1/3] board: Add sam9x60_curiosity support Durai Manickam KR
2022-04-04  5:53 ` [PATCHv3 2/3] ARM: dts: Add device tree files for sam9x60_curiosity Durai Manickam KR
2022-04-04  5:53 ` [PATCHv3 3/3] configs: Add sam9x60_curiosity_mmc_defconfig Durai Manickam KR
2022-04-27  6:00 ` Eugen.Hristev [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=ebadbbbc-d612-b2a6-3667-31990ff22aee@microchip.com \
    --to=eugen.hristev@microchip.com \
    --cc=Durai.ManickamKR@microchip.com \
    --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