archive mirror
 help / color / mirror / Atom feed
From: "Milton Miller II" <>
Subject: Re:  AST2600: Linux driver support for SPI controller
Date: Mon, 19 Jul 2021 16:32:10 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On July 19, 2021,  VINOTHKUMAR RK wrote:
>Hello all,
>This is regarding SPI controller driver support in OpenBMC.
>Here is the scenario: Three devices connected over same SPI
>controller as mentioned below:
>Firmware SPI Memory Controller (BSPI): (0x1E620000):
>    - Flash 0 (CS0)
>    - Flash 1 (CS1)
>    - MCU/CPLD (CS2)
>When I look at the OpenBMC Linux repository, I could find
>'aspeed-smc.c' driver under the MTD subsystem, so this seems to work
>only for flash devices.
>Do we've any other driver support or a solution to handle all the
>three devices? Any help/suggestions would be appreciated.

I was involved with the driver you found before Cedric took it 

I am not aware of anyone writing a generic SPI acccess driver.   
The hardwaredoes have a user mode that does not auto-sequence, but 
as I remember its limited in that it can not read and write data 
at the same time and is limited to transfers that are multiples of 
a byte.

If your MCU/CPLD can live with these limitations then you or 
someone can integrate a spi layer driver into the current 

Note on the 2600 the hardware for the host is the same as the 
hardware for the BMC.  It may be easier to develop spi mode on 
that port because it could be developed while running with the 
BMC from existing driver.  Alternatively it could be developed 
on a system that runs on eMMC.


  reply	other threads:[~2021-07-19 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 13:02 AST2600: Linux driver support for SPI controller VINOTHKUMAR RK
2021-07-19 16:32 ` Milton Miller II [this message]
2021-07-19 18:38 ` Patrick Williams

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).