Message ID | 20220706042039.5763-1-nandhini.srikandan@intel.com |
---|---|
Headers | show
Return-Path: <linux-spi-owner@kernel.org> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EAC25C433EF for <linux-spi@archiver.kernel.org>; Wed, 6 Jul 2022 04:26:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229922AbiGFE0V (ORCPT <rfc822;linux-spi@archiver.kernel.org>); Wed, 6 Jul 2022 00:26:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46176 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229522AbiGFE0T (ORCPT <rfc822;linux-spi@vger.kernel.org>); Wed, 6 Jul 2022 00:26:19 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E1CF1BE86; Tue, 5 Jul 2022 21:26:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657081579; x=1688617579; h=from:to:cc:subject:date:message-id; bh=CpMC0XBJdC4PpHI7lyH7PNL5lXsRI1A2EpfQo/IPNhk=; b=W9jK1Be0OhZUmcVmOP6Ws+H7oNvmkvjXftbSM8qjKXXgttRnDPl2D1ty YO7E2JBUhqRoL+rnDGCZWCsw2eRJ1ntQP8a8LXOmbzd/ojU5Gdt0Fd7Xc ntYOQYM4lWjqMECgyWUsfKLIJIPkORdJro7SwRP4i4VXH650g2y9KwIbj eJUTNN/DTKKU3Eg5qvDs+lxenUneeJN/EpDAoKPPBF6/b5vT0IKJo2Ph5 c/J0VGZFLSELpTqZK6ovDzeqHi9pv8Jkr1CZh5lSnSq2TYDmuOy8V+vP9 O7pPA3Z5PujBo9elopr79e8tS/fafkUBz55nCzp4tDRFIcUxZNGvhAC8q g==; X-IronPort-AV: E=McAfee;i="6400,9594,10399"; a="283663236" X-IronPort-AV: E=Sophos;i="5.92,248,1650956400"; d="scan'208";a="283663236" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2022 21:26:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.92,248,1650956400"; d="scan'208";a="769895409" Received: from srikandan-ilbpg12.png.intel.com ([10.88.229.69]) by orsmga005.jf.intel.com with ESMTP; 05 Jul 2022 21:26:14 -0700 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 v5 0/4] Add support for Intel Thunder Bay SPI controller Date: Wed, 6 Jul 2022 12:20:35 +0800 Message-Id: <20220706042039.5763-1-nandhini.srikandan@intel.com> X-Mailer: git-send-email 2.17.1 Precedence: bulk List-ID: <linux-spi.vger.kernel.org> X-Mailing-List: linux-spi@vger.kernel.org |
Series |
Add support for Intel Thunder Bay SPI controller
|
expand
|
From: Nandhini Srikandan <nandhini.srikandan@intel.com> Hi, 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 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 v4: 1) Newly introduced in v5 as seperate patch. Patch 2: -------- Changes from v4/v3/v2/v1: 1) No change in this patch. Patch 3: -------- 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 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(-)