All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <p.yadav@ti.com>
To: Vaishnav Achath <vaishnav.a@ti.com>
Cc: <hs@denx.de>, <u-boot@lists.denx.de>, <sjg@chromium.org>,
	<mr.nuke.me@gmail.com>, <jh80.chung@samsung.com>,
	<michal.simek@amd.com>, <marek.behun@nic.cz>, <pali@kernel.org>,
	<sr@denx.de>, <marex@denx.de>, <ricardo@foundries.io>,
	<vigneshr@ti.com>, <s-anna@ti.com>, <kishon@ti.com>,
	<j-keerthy@ti.com>
Subject: Re: [PATCH v2 1/2] common: spl: spl_spi: add support for dynamic override of sf bus
Date: Tue, 31 May 2022 14:29:20 +0530	[thread overview]
Message-ID: <20220531085920.tlnnis44q342ittb@ti.com> (raw)
In-Reply-To: <20220511060352.28140-2-vaishnav.a@ti.com>

On 11/05/22 11:33AM, Vaishnav Achath wrote:
> Currently the SPI flash to load from is defined through the compile
> time config CONFIG_SF_DEFAULT_BUS and CONFIG_SF_DEFAULT_CS, this
> prevents the loading of binaries from different SPI flash using the
> same build.E.g. supporting QSPI flash boot and OSPI flash boot
> on J721E platform is not possible due to this limitation.
> 
> This commit adds lookup functions spl_spi_boot_bus()
> and spl_spi_boot_cs for identifying the flash device based on the
> selected boot device, when not overridden the lookup functions are
> weakly defined in common/spl/spl_spi.c.
> 
> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>

Reviewed-by: Pratyush Yadav <p.yadav@ti.com>

-- 
Regards,
Pratyush Yadav
Texas Instruments Inc.

  parent reply	other threads:[~2022-05-31  8:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11  6:03 [PATCH v2 0/2] Add support for dynamic overriding of default SF bus Vaishnav Achath
2022-05-11  6:03 ` [PATCH v2 1/2] common: spl: spl_spi: add support for dynamic override of sf bus Vaishnav Achath
2022-05-11  8:24   ` Heiko Schocher
2022-05-12  6:28     ` Vaishnav Achath
2022-05-31  8:59   ` Pratyush Yadav [this message]
2022-05-11  6:03 ` [PATCH v2 2/2] arm: k3: j721e: add dynamic sf bus override support for j721e Vaishnav Achath
2022-05-31 10:59   ` Pratyush Yadav

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=20220531085920.tlnnis44q342ittb@ti.com \
    --to=p.yadav@ti.com \
    --cc=hs@denx.de \
    --cc=j-keerthy@ti.com \
    --cc=jh80.chung@samsung.com \
    --cc=kishon@ti.com \
    --cc=marek.behun@nic.cz \
    --cc=marex@denx.de \
    --cc=michal.simek@amd.com \
    --cc=mr.nuke.me@gmail.com \
    --cc=pali@kernel.org \
    --cc=ricardo@foundries.io \
    --cc=s-anna@ti.com \
    --cc=sjg@chromium.org \
    --cc=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    --cc=vaishnav.a@ti.com \
    --cc=vigneshr@ti.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.