From: nandhini.srikandan@intel.com
To: fancer.lancer@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, mgross@linux.intel.com,
kris.pan@intel.com, kenchappa.demakkanavar@intel.com,
furong.zhou@intel.com, mallikarjunappa.sangannavar@intel.com,
mahesh.r.vaidya@intel.com, nandhini.srikandan@intel.com,
rashmi.a@intel.com
Subject: [PATCH v6 0/4] Add support for Intel Thunder Bay SPI controller
Date: Wed, 13 Jul 2022 12:22:19 +0800 [thread overview]
Message-ID: <20220713042223.1458-1-nandhini.srikandan@intel.com> (raw)
From: Nandhini Srikandan <nandhini.srikandan@intel.com>
This patch enables support for DW SPI on Intel Thunder Bay.
This patch set also enables master mode for latest Designware SPI versions.
Patch 1: Fixed dw_spi_ip_is macro with the missing underscore.
Patch 2: DW SPI DT bindings for Intel Thunder Bay SoC.
Patch 3: Adds master mode support for Designware SPI controller.
Patch 4: Adds support for Designware SPI on Intel Thunder Bay SoC.
The driver is tested on Keem Bay and Thunder Bay evaluation board
Summary:
Changes from v5:
1) Added changelog for Patch 1.
2) Added Acked-by and Reviewed-by to applicable patches.
3) There are no other changes other than changelog in any of the patches.
Changes from v4:
1) Reordered master mode selection patch and Thunder Bay support patch.
2) The typo fix for macro dw_spi_ip_is is made into seperate patch.
Changes from v3:
1) Dropped SSTE support in this patch.
2) Rebased to the latest code.
Changes from v2:
1) SSTE support made using dt and created seperate patches.
2) SPI controller master mode selection made common to all DW SPI controllers.
3) Using a common init function for both keem bay and thunder bay.
Changes from v1:
1) Designware CR0 specific macros are named in a generic way.
2) SPI CAP macros are named in generic way rather than naming project specific.
3) SPI KEEM BAY specific macros are replaced by generic macros.
4) Resued the existing SPI deassert API instead of adding another reset.
Changes in patches:
Patch 1:
--------
Changes from v5:
1) Added changelog
Changes from v4:
1) Newly introduced in v5 as seperate patch.
Patch 2:
--------
Changes from v5/v4/v3/v2/v1:
1) No change in this patch.
Patch 3:
--------
Changes from v5:
1) No changes.
Changes from v4:
1) Reordered the patch.
2) Setting CTRLR0 BIT31 is done conditionally for 1.02a version.
Changes from v3:
1) Corrected dw_spi_ip_is macro with the missing underscore.
2) Setting CTRLR0 BIT31 without any condition check as in older version of
DW SPI controller this bit is reserved.
Changes from v2/v1:
1)Newly introduced in v3 to make master mode selection as seperate patch.
Patch 4:
--------
Changes from v5:
1) No changes.
Changes from v4:
1) Reordered the patch.
Changes from v3:
1) No changes.
Changes from v2:
1) Init function is made common for Keem Bay and Thunder Bay.
Thanks & Regards,
Nandhini
Nandhini Srikandan (4):
spi: dw: Fix IP-core versions macro
dt-bindings: spi: Add bindings for Intel Thunder Bay SOC
spi: dw: Add support for master mode selection for DWC SSI controller
spi: dw: Add support for Intel Thunder Bay SPI controller
.../devicetree/bindings/spi/snps,dw-apb-ssi.yaml | 2 ++
drivers/spi/spi-dw-core.c | 5 +++--
drivers/spi/spi-dw-mmio.c | 8 ++++----
drivers/spi/spi-dw.h | 13 +++----------
4 files changed, 12 insertions(+), 16 deletions(-)
--
2.17.1
next reply other threads:[~2022-07-13 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 4:22 nandhini.srikandan [this message]
2022-07-13 4:22 ` [PATCH v6 1/4] spi: dw: Fix IP-core versions macro nandhini.srikandan
2022-07-13 5:31 ` Serge Semin
2022-07-13 4:22 ` [PATCH v6 2/4] dt-bindings: spi: Add bindings for Intel Thunder Bay SOC nandhini.srikandan
2022-07-13 4:22 ` [PATCH v6 3/4] spi: dw: Add support for master mode selection for DWC SSI controller nandhini.srikandan
2022-07-13 4:22 ` [PATCH v6 4/4] spi: dw: Add support for Intel Thunder Bay SPI controller nandhini.srikandan
2022-07-13 14:41 ` [PATCH v6 0/4] " Mark Brown
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=20220713042223.1458-1-nandhini.srikandan@intel.com \
--to=nandhini.srikandan@intel.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=furong.zhou@intel.com \
--cc=kenchappa.demakkanavar@intel.com \
--cc=kris.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mahesh.r.vaidya@intel.com \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=rashmi.a@intel.com \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).