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] sf: About sandbox flash driver
Date: Mon, 11 Jan 2016 09:58:38 -0700	[thread overview]
Message-ID: <CAPnjgZ1JfEWXAbrKUHykYNMferpTp-8wna1Yu+BA4CeXuKuisg@mail.gmail.com> (raw)
In-Reply-To: <CAD6G_RQFfMOX2Ef5bTwsG=oqqiavKVqhf1Mp4dt7TZmdP7ZC8A@mail.gmail.com>

Hi Jagan,


On 8 January 2016 at 03:47, Jagan Teki <jteki@openedev.com> wrote:
> Hi Simon,
>
> On 8 January 2016 at 01:19, Simon Glass <sjg@chromium.org> wrote:
>> Hi Jagan,
>>
>> On 30 December 2015 at 10:03, Jagan Teki <jteki@openedev.com> wrote:
>>> Hi Simon,
>>>
>>> Few question wrt sandbox flash driver - drivers/mtd/spi/sandbox.c
>>>
>>> 1) Does this driver used for creating flash emulation environment? or
>>> something else?
>>
>> It is an emulation driver, meant to emulate a SPI flash device. See
>> sandbox_sf_emul_ops - the sandbox_sf_xfer() receives a SPI message
>> from U-Boot and produces a reply.
>>
>>> 2) Can't it use spi_flash.c core for all spi flash operations, how
>>> different is this?
>>
>> That is for talking to SPI flash devices I think, rather than emulating one.
>
> Yes, that I understood. is it possible to modify this to use spi_flash
> core? Because we need to maintain the spi_flash_params separately for
> this, see my last series for reference[1] I have moved flash_prams
> inside spi_flash core and old ones to sandbox

I'm sure it could be changed. At present it uses
spi_flash_params_table but it could be changed to use a different
table.

>
> [1] http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/246568
>
> thanks!
> --
> Jagan.

Regards,
Simon

      reply	other threads:[~2016-01-11 16:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 17:03 [U-Boot] sf: About sandbox flash driver Jagan Teki
2016-01-07 19:49 ` Simon Glass
2016-01-08 10:47   ` Jagan Teki
2016-01-11 16:58     ` Simon Glass [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=CAPnjgZ1JfEWXAbrKUHykYNMferpTp-8wna1Yu+BA4CeXuKuisg@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.