From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Arnd Bergmann <arnd@arndb.de>, Joao Pinto <Joao.Pinto@synopsys.com>
Cc: vinholikatti@gmail.com, julian.calaby@gmail.com,
akinobu.mita@gmail.com, hch@infradead.org, mark.rutland@arm.com,
robh@kernel.org, gbroner@codeaurora.org, subhashj@codeaurora.org,
CARLOS.PALMINHA@synopsys.com, ijc+devicetree@hellion.org.uk,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v9 3/3] add support for DWC UFS Host Controller
Date: Thu, 3 Mar 2016 11:39:05 +0000 [thread overview]
Message-ID: <56D82259.3020907@synopsys.com> (raw)
In-Reply-To: <5606371.ipFvUUmgV9@wuerfel>
Hi Arnd,
On 3/2/2016 7:55 PM, Arnd Bergmann wrote:
> On Wednesday 02 March 2016 16:46:47 Joao Pinto wrote:
>> On 2/19/2016 3:03 PM, Arnd Bergmann wrote:
>>> On Thursday 18 February 2016 17:20:27 Joao Pinto wrote:
Facts:
- Test Chip type are currently not detectable in runtime through the controller
- In the future the Test Chip version will be available in the controller
- Test Chip initialization is different for each type
- The IP Core version is 1.40a
- Test Chip version is 6.00
- Teh UFS version is 2.0
Suggested driver architecture:
Platform setup:
tc-dwc-g210-pltfrm --> tc-dwc-g210 --> ufshcd-dwc-pltfrm --> ufshcd-dwc --> ufs
The test chip platform driver could be called through 2 compatibility strings.
indicating the chip's version and bit type:
"snps, g210-tc-6.00-20bit"
"snps, g210-tc-6.00-40bit"
The device tree node would have additional info compatibility strings as the DWC
IP core version and UFS version:
"snps, dwc-ufshcd-1.40a"
"jedec, ufs-2.0"
PCI based setup:
tc-dwc-g210-pci --> tc-dwc-g210 --> ufshcd-dwc-pci --> ufshcd-dwc --> ufs
The test chip type would be configured by a parameter to be passed in the kernel
boot args: tc_type = 20 (20-bit) or tc_type = 40 (40-bit)
Having this in mind the KConfig would be:
"config SCSI_UFS_DWC_HOOKS
bool
config SCSI_UFS_DWC_PLAT
tristate "DesignWare UFS controller platform glue driver"
depends on SCSI_UFSHCD_PLATFORM
select SCSI_UFS_DWC_HOOKS
help
This selects the DesignWare UFS host controller platform glue driver.
Select this if you have a DesignWare UFS controller on Platform bus.
If unsure, say N.
config SCSI_UFS_DWC_PCI
tristate "DesignWare UFS controller pci glue driver"
depends on SCSI_UFSHCD_PCI
select SCSI_UFS_DWC_HOOKS
help
This selects the DesignWare UFS host controller pci glue driver.
Select this if you have a DesignWare UFS controller on pci bus.
If unsure, say N.
config SCSI_UFS_DWC_TC
bool "Support for the Synopsys Test Chip"
depends on SCSI_UFS_DWC_HOOKS && (SCSI_UFSHCD_PCI || SCSI_UFS_DWC_PLAT)
---help---
Synopsys Test Chip is a Phy for prototyping purposes.
This selects the support for the Synopsys Test Chip.
Select this if you have a Synopsys Test Chip.
If unsure, say N."
Agree with the approach?
Thanks for the help.
Joao
next prev parent reply other threads:[~2016-03-03 11:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 15:25 [PATCH v8 0/3] add support for DWC UFS Controller Joao Pinto
2016-02-15 15:25 ` [PATCH v8 1/3] fixed typo in ufshcd-pltfrm Joao Pinto
2016-02-15 15:25 ` [PATCH v8 2/3] added UFS 2.0 capabilities Joao Pinto
2016-02-18 14:38 ` Rob Herring
2016-02-15 15:25 ` [PATCH v8 3/3] add support for DWC UFS Host Controller Joao Pinto
2016-02-18 14:38 ` Rob Herring
[not found] ` <5c806ca29340923831e05a729bbb6557d7ce83cb.1455549222.git.jpinto-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-02-19 15:03 ` [PATCH v9 " Arnd Bergmann
2016-03-02 16:46 ` Joao Pinto
2016-03-02 19:55 ` Arnd Bergmann
2016-03-03 11:39 ` Joao Pinto [this message]
[not found] ` <56D82259.3020907-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>
2016-03-03 12:04 ` Arnd Bergmann
2016-03-03 13:52 ` Joao Pinto
2016-03-03 14:12 ` Arnd Bergmann
2016-03-03 14:17 ` Joao Pinto
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=56D82259.3020907@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=akinobu.mita@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gbroner@codeaurora.org \
--cc=hch@infradead.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=julian.calaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=subhashj@codeaurora.org \
--cc=vinholikatti@gmail.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 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).