Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp542384ybe; Wed, 18 Sep 2019 23:05:29 -0700 (PDT) X-Google-Smtp-Source: APXvYqytks9zA6WWVplpVypzjYDCekV/UGrCvt3iYwXrRCdGg/0TDmwZ/ij2ON4NywL+p2hH9o1N X-Received: by 2002:a50:99d5:: with SMTP id n21mr14351545edb.50.1568873128969; Wed, 18 Sep 2019 23:05:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568873128; cv=none; d=google.com; s=arc-20160816; b=pumB1Jr7uP4yF0olstbhry+xjq5h8uB0T8rOIPAXUHWQxIDQDAhkU7JSuRZuhjIt0e pLC+re6UmhSfcitiUJmFGX21iqQmmOnHmapWmYjaNSLiL2IeITy9DCxt8D6wADZsQEIj 8pqpj2mud0awE/cXFmYJAVQDgiGbE9Akps5b13ldTdd2Oik6CYSOT+fw+Kf+ytdrmsHr YHjy0xThiMfoFEv/9NwvQlNL4PTCuYTDCoyMc3k4Qj4MdzU20QAn62ZoHsr+RweBAHY4 UH7Js+kLejuQOLqBdiji8z0NE+LtQdkblzWJW3eVnmpn2aWh8IkWmTNKepbY1KQnX6sX CGLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=r+SG790V4ebwKVus6Xa751GmxfgXlQdbURb0ML83yRM=; b=oNDn/saYKqCRtCzu/3zRUl5to+sdauqaSnK472sYN3Afht1RmdW2OlwTXHLInAGYG8 MQoP9GS0LdTrS228Kh0wxdQQbJk4xU4GxKKsY7u+2305Enr0zz3M+IfgtmJdolpi/1cw tc88j0MLP+NfmouYTw15OpX0HPalyoJZsfbrvfDfRiOHRSKK9I4y6zt8IHQrflCmE/5d bRfRFJmP5kyIkZ7TxpDo7+5mnFpA1VrQ8QG3O4qPeBBQLRN9gkBvld1TqgCzEr9yAVbi hGQWPxvdlC9hSrhyM2xMPzn1lYBmJBoUmVhFeqIzXjoBwKbVqpAkWNGIKswoJ6hT7jIb 5J4Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e21si4348097edb.164.2019.09.18.23.05.05; Wed, 18 Sep 2019 23:05:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730949AbfISFpG (ORCPT + 99 others); Thu, 19 Sep 2019 01:45:06 -0400 Received: from mga02.intel.com ([134.134.136.20]:17613 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725887AbfISFpG (ORCPT ); Thu, 19 Sep 2019 01:45:06 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Sep 2019 22:45:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,522,1559545200"; d="scan'208";a="177944875" Received: from linux.intel.com ([10.54.29.200]) by orsmga007.jf.intel.com with ESMTP; 18 Sep 2019 22:45:05 -0700 Received: from [10.226.38.20] (unknown [10.226.38.20]) by linux.intel.com (Postfix) with ESMTP id A56445802C8; Wed, 18 Sep 2019 22:45:03 -0700 (PDT) Subject: Re: [PATCH v1 2/2] spi: cadence-qspi: Add QSPI support for Intel LGM SoC To: Mark Brown Cc: robh+dt@kernel.org, mark.rutland@arm.com, linux-spi@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, cheol.yong.kim@intel.com, qi-ming.wu@intel.com References: <20190916073843.39618-1-vadivel.muruganx.ramuthevar@linux.intel.com> <20190916073843.39618-3-vadivel.muruganx.ramuthevar@linux.intel.com> <20190916113255.GA4352@sirena.co.uk> <466b41c1-3d65-0bf4-6db7-d3b3e06b107b@linux.intel.com> <20190917153650.GF3524@sirena.co.uk> <20190918120846.GH2596@sirena.co.uk> From: "Ramuthevar, Vadivel MuruganX" Message-ID: Date: Thu, 19 Sep 2019 13:45:02 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: <20190918120846.GH2596@sirena.co.uk> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Mark, ?? Thank you for the comments and queries. On 18/9/2019 8:08 PM, Mark Brown wrote: > On Wed, Sep 18, 2019 at 01:59:06PM +0800, Ramuthevar, Vadivel MuruganX wrote: >> On 17/9/2019 11:36 PM, Mark Brown wrote: >>> On Tue, Sep 17, 2019 at 10:11:28AM +0800, Ramuthevar, Vadivel MuruganX wrote: >>>> *??? spi-cadence.c* in *drivers/spi/*, which supports very old legacy >>>> cadence-spi based devices(normal) >>>> *??? cadence-quadspi.c(drivers/mtd/spi-nor/)* : specific support to SPI-NOR >>>> flash with new spi-nor layer. >>>> ??? all the API's in this driver purely on spi-nor specific, so couldn't >>>> proceed to adapt. >>> Are these completely separate IPs or are they just different versions of >>> the same IP? >> These are same IPs , but different features Enabled/Disabled depends upon >> the SoC vendors. >> for e.g: Intel LGM SoC uses the same IP, but without DMA and Direct access >> controller. >> also dedicated support to flash devices. > If it's different versions of the same IP then everything should be in > one driver with the optional features enabled depending on what's in a > given system. Agreed!, I am trying to adapt the driver/mtd/spi-nor/cadence-quadspi.c and newly sent patches in a single driver file, also trying to use spi_mem_ops framework. With Best Regards Vadivel