All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chalapathi V <chalapathi.v@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, fbarrat@linux.ibm.com, npiggin@gmail.com,
	clg@kaod.org, calebs@us.ibm.com, chalapathi.v@ibm.com,
	saif.abrar@linux.vnet.ibm.com
Subject: Re: [PATCH v1 0/5] hw/ppc: SPI model
Date: Fri, 1 Mar 2024 21:47:18 +0530	[thread overview]
Message-ID: <2aef5ff8-bdae-437e-892b-25e4fe684335@linux.ibm.com> (raw)
In-Reply-To: <20240207160833.3437779-1-chalapathi.v@linux.ibm.com>

Hello,

I would greatly appreciate the review comments/suggestions on PATCH V1.

Thank You and Regards,

Chalapathi

On 07-02-2024 21:38, Chalapathi V wrote:
> Hello,
>
> In this series of patchset, SPI controller and responder models
> for Power10 processor are modelled.
>
> Serial peripheral interface provides full-duplex synchronous serial
> communication between single controller and multiple responder devices.
>
> The current configuration supports a single SPI controller reside on the
> SPI bus. In p10, SPI controller device model supports a connection to a
> single SPI responder such as SPI seeproms, TPM, flash device and an ADC
> controller.
>
> SPI controller model is divided into configuration unit, sequencer FSM
> and shifter engine. All SPI function control is mapped into the SPI register
> space to enable full control by firmware.
>
> SPI configuration component is modelled which contains all SPI configuration
> and status registers as well as the hold registers for data to be sent or
> having been received.
> Shift engine performs serialization and de-serialization according to the
> control by the sequencer and according to the setup defined in the
> configuration registers.
> Sequencer implements the main control logic and
> FSM to handle data transmit and data receive control of the shift engine.
>
> Microchip's 25CSM04 SEEPROM device is modelled and connected to SPI bus
> "spi_bus2" of SPI controller "PIB_SPIC[2]".
>
> Patches overview in V1.
> PATCH1: Create a SPI responder model which includes responder methods
>          and SPI bus implementation.
> PATCH2: Create a SPI controller model and implement configuration unit
>          to model SCOM registers.
> PATCH3: SPI controller model: implement sequencer FSM and shift engine.
> PATCH4: create SPI SEEPROM model.
> PATCH5: Connect SPI controllers to p10 chip and create keystore seeprom
>          device on spi_bus2 of PIB_SPIC[2].
>
> Thank You,
> Chalapathi
>
> Chalapathi V (5):
>    hw/ppc: SPI responder model
>    hw/ppc: SPI controller model - registers implementation
>    hw/ppc: SPI controller model - sequencer and shifter
>    hw/ppc: SPI SEEPROM model
>    hw/ppc: SPI controller wiring to P10 chip and create seeprom device
>
>   include/hw/ppc/pnv_chip.h           |    4 +
>   include/hw/ppc/pnv_spi_controller.h |  101 ++
>   include/hw/ppc/pnv_spi_responder.h  |  109 ++
>   include/hw/ppc/pnv_spi_seeprom.h    |   70 ++
>   include/hw/ppc/pnv_xscom.h          |    3 +
>   hw/ppc/pnv.c                        |   32 +
>   hw/ppc/pnv_spi_controller.c         | 1609 +++++++++++++++++++++++++++
>   hw/ppc/pnv_spi_responder.c          |  166 +++
>   hw/ppc/pnv_spi_seeprom.c            |  989 ++++++++++++++++
>   hw/ppc/meson.build                  |    3 +
>   10 files changed, 3086 insertions(+)
>   create mode 100644 include/hw/ppc/pnv_spi_controller.h
>   create mode 100644 include/hw/ppc/pnv_spi_responder.h
>   create mode 100644 include/hw/ppc/pnv_spi_seeprom.h
>   create mode 100644 hw/ppc/pnv_spi_controller.c
>   create mode 100644 hw/ppc/pnv_spi_responder.c
>   create mode 100644 hw/ppc/pnv_spi_seeprom.c
>


  parent reply	other threads:[~2024-03-01 16:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 16:08 [PATCH v1 0/5] hw/ppc: SPI model Chalapathi V
2024-02-07 16:08 ` [PATCH v1 1/5] hw/ppc: SPI responder model Chalapathi V
2024-03-08 16:00   ` Stefan Berger
2024-02-07 16:08 ` [PATCH v1 2/5] hw/ppc: SPI controller model - registers implementation Chalapathi V
2024-03-07 18:54   ` Stefan Berger
2024-03-07 19:11     ` Stefan Berger
2024-03-08 15:17     ` Stefan Berger
2024-02-07 16:08 ` [PATCH v1 3/5] hw/ppc: SPI controller model - sequencer and shifter Chalapathi V
2024-03-08 19:36   ` Stefan Berger
2024-02-07 16:08 ` [PATCH v1 4/5] hw/ppc: SPI SEEPROM model Chalapathi V
2024-03-08 15:14   ` Stefan Berger
2024-02-07 16:08 ` [PATCH v1 5/5] hw/ppc: SPI controller wiring to P10 chip and create seeprom device Chalapathi V
2024-03-01 16:17 ` Chalapathi V [this message]
2024-03-01 16:36   ` [PATCH v1 0/5] hw/ppc: SPI model Cédric Le Goater
2024-03-01 18:33     ` Chalapathi V

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=2aef5ff8-bdae-437e-892b-25e4fe684335@linux.ibm.com \
    --to=chalapathi.v@linux.ibm.com \
    --cc=calebs@us.ibm.com \
    --cc=chalapathi.v@ibm.com \
    --cc=clg@kaod.org \
    --cc=fbarrat@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=saif.abrar@linux.vnet.ibm.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.