From: Greg Ungerer <gerg@linux-m68k.org> To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>, linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: fabio.estevam@nxp.com, shawnguo@kernel.org, kernel@pengutronix.de Subject: Re: [PATCH 2/2] spi: imx: fix use of native chip-selects with devicetree Date: Tue, 21 Mar 2017 12:05:20 +1000 [thread overview] Message-ID: <4a8449d9-cc38-d642-0853-246f46ee7059@linux-m68k.org> (raw) In-Reply-To: <f1cf2001-28b4-6a74-b98a-13336d74ff9d@mentor.com> Hi Vladimir, On 20/03/17 23:22, Vladimir Zapolskiy wrote: > On 03/17/2017 07:03 AM, Greg Ungerer wrote: >> The commonly used mechanism of specifying the hardware or native >> chip-select on an SPI device in devicetree (that is "cs-gpios = <0>") >> does not result in the native chip-select being configured for use. >> So external SPI devices that require use of the native chip-select >> will not work. >> >> You can successfully specify native chip-selects if using a platform >> setup by specifying the cs-gpio as negative offset by 32. And that >> works correctly. You cannot use the same method in devicetree. >> >> The logic in the spi-imx.c driver during probe uses core spi function >> of_spi_register_master() in spi.c to parse the "cs-gpios" devicetree tag. >> For valid GPIO values that will be recorded for use, all other entries in >> the cs_gpios list will be set to -ENOENT. So entries like "<0>" will be >> set to -ENOENT in the cs_gpios list. >> >> When the SPI device registers are setup the code will use the GPIO >> listed in the cs_gpios list for the desired chip-select. If the cs_gpio >> is less then 0 then it is intended to be for a native chip-select, and >> its cs_gpio value is added to 32 to get the chipselect number to use. >> Problem is that with devicetree this can only ever be -ENOENT (which >> is -2), and that alone results in an invalid chip-select number. But also >> doesn't allow selection of the native chip-select at all. >> >> To fix, if the cs_gpio specified for this spi device is not a >> valid GPIO then use the "chip_select" (that is the native chip-select >> number) for hardware setup. >> > > Can you please share an example of "cs-gpios" property for a particular > case, which I'm able to test? It is an Atmel AT93C66A EEPROM connected > to CSPI1 and sitting on chip select 2 (= selected by CSPI1_SS2), there > is no other SPI devices on CSPI1. Is the AT93C66A going to work if you use native chip selects? I have an iMX25 based board with a NOR flash on SPI1 using a GPIO chip select, and on SPI2 a Silicon Labs 32260 SLIC using the native chip select 1. It requires the chip select line to be asserted and de-asserted between each byte, as done when using the native chip select setup of the iMX SPI module. Anyway, the cs-gpio I use is: cs-gpios = <0>, <0>, <0>, <0>; > Since I raise the question, please add the correspondent updates and > and an example to Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt Ok. There is a few other devicetrees in arc/arm/boot/dts that use the "<0>" notation for cs-gpios. Documentation/devicetree/bindings/spi/spi-davinci.txt does describe its meaning. > In fact my expectation would be to have a device description like one > below: > > &spi1 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_cspi1>; > > eeprom@2 { > compatible = "atmel,at93c66a"; > reg = <2>; > spi-cs-high; > spi-max-frequency = <1000000>; > }; > }; > > Note, that there is no cs-gpios property at all, which is mandatory > at the moment, and unit address / reg property defines chip select > number. Ideally it would be allowed to have no cs-gpios at all. But currently the spi-imx driver explicitly fails on this: spi.1: No CS GPIOs available As an example my devicetree entry is similar to your above, but it has "cs-gpios = <0>, <0>, <0>, <0>;" as well. Thats all. > For that type of bindings locally I have a hackish spi-imx driver change, > which supports this option, but I'm unsure if it is universal enough. Do you mean supporting no cs-gpios tag? That would be nice, but it would seem not many users of this are using native chip selects. Regards Greg
WARNING: multiple messages have this Message-ID (diff)
From: gerg@linux-m68k.org (Greg Ungerer) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/2] spi: imx: fix use of native chip-selects with devicetree Date: Tue, 21 Mar 2017 12:05:20 +1000 [thread overview] Message-ID: <4a8449d9-cc38-d642-0853-246f46ee7059@linux-m68k.org> (raw) In-Reply-To: <f1cf2001-28b4-6a74-b98a-13336d74ff9d@mentor.com> Hi Vladimir, On 20/03/17 23:22, Vladimir Zapolskiy wrote: > On 03/17/2017 07:03 AM, Greg Ungerer wrote: >> The commonly used mechanism of specifying the hardware or native >> chip-select on an SPI device in devicetree (that is "cs-gpios = <0>") >> does not result in the native chip-select being configured for use. >> So external SPI devices that require use of the native chip-select >> will not work. >> >> You can successfully specify native chip-selects if using a platform >> setup by specifying the cs-gpio as negative offset by 32. And that >> works correctly. You cannot use the same method in devicetree. >> >> The logic in the spi-imx.c driver during probe uses core spi function >> of_spi_register_master() in spi.c to parse the "cs-gpios" devicetree tag. >> For valid GPIO values that will be recorded for use, all other entries in >> the cs_gpios list will be set to -ENOENT. So entries like "<0>" will be >> set to -ENOENT in the cs_gpios list. >> >> When the SPI device registers are setup the code will use the GPIO >> listed in the cs_gpios list for the desired chip-select. If the cs_gpio >> is less then 0 then it is intended to be for a native chip-select, and >> its cs_gpio value is added to 32 to get the chipselect number to use. >> Problem is that with devicetree this can only ever be -ENOENT (which >> is -2), and that alone results in an invalid chip-select number. But also >> doesn't allow selection of the native chip-select at all. >> >> To fix, if the cs_gpio specified for this spi device is not a >> valid GPIO then use the "chip_select" (that is the native chip-select >> number) for hardware setup. >> > > Can you please share an example of "cs-gpios" property for a particular > case, which I'm able to test? It is an Atmel AT93C66A EEPROM connected > to CSPI1 and sitting on chip select 2 (= selected by CSPI1_SS2), there > is no other SPI devices on CSPI1. Is the AT93C66A going to work if you use native chip selects? I have an iMX25 based board with a NOR flash on SPI1 using a GPIO chip select, and on SPI2 a Silicon Labs 32260 SLIC using the native chip select 1. It requires the chip select line to be asserted and de-asserted between each byte, as done when using the native chip select setup of the iMX SPI module. Anyway, the cs-gpio I use is: cs-gpios = <0>, <0>, <0>, <0>; > Since I raise the question, please add the correspondent updates and > and an example to Documentation/devicetree/bindings/spi/fsl-imx-cspi.txt Ok. There is a few other devicetrees in arc/arm/boot/dts that use the "<0>" notation for cs-gpios. Documentation/devicetree/bindings/spi/spi-davinci.txt does describe its meaning. > In fact my expectation would be to have a device description like one > below: > > &spi1 { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_cspi1>; > > eeprom at 2 { > compatible = "atmel,at93c66a"; > reg = <2>; > spi-cs-high; > spi-max-frequency = <1000000>; > }; > }; > > Note, that there is no cs-gpios property at all, which is mandatory > at the moment, and unit address / reg property defines chip select > number. Ideally it would be allowed to have no cs-gpios at all. But currently the spi-imx driver explicitly fails on this: spi.1: No CS GPIOs available As an example my devicetree entry is similar to your above, but it has "cs-gpios = <0>, <0>, <0>, <0>;" as well. Thats all. > For that type of bindings locally I have a hackish spi-imx driver change, > which supports this option, but I'm unsure if it is universal enough. Do you mean supporting no cs-gpios tag? That would be nice, but it would seem not many users of this are using native chip selects. Regards Greg
next prev parent reply other threads:[~2017-03-21 2:05 UTC|newest] Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-17 5:03 [PATCH 0/2] spi: imx: native chip selects and devicetree Greg Ungerer 2017-03-17 5:03 ` Greg Ungerer 2017-03-17 5:03 ` [PATCH 1/2] spi: imx: set correct chip_select in platform setup Greg Ungerer 2017-03-17 5:03 ` Greg Ungerer [not found] ` <1489726983-17706-2-git-send-email-gerg-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-20 7:38 ` Shawn Guo 2017-03-20 7:38 ` Shawn Guo 2017-03-20 11:52 ` Greg Ungerer 2017-03-20 11:52 ` Greg Ungerer [not found] ` <1489726983-17706-1-git-send-email-gerg-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-17 5:03 ` [PATCH 2/2] spi: imx: fix use of native chip-selects with devicetree Greg Ungerer 2017-03-17 5:03 ` Greg Ungerer 2017-03-20 7:39 ` Shawn Guo 2017-03-20 7:39 ` Shawn Guo [not found] ` <1489726983-17706-3-git-send-email-gerg-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-20 13:22 ` Vladimir Zapolskiy 2017-03-20 13:22 ` Vladimir Zapolskiy 2017-03-21 2:05 ` Greg Ungerer [this message] 2017-03-21 2:05 ` Greg Ungerer [not found] ` <4a8449d9-cc38-d642-0853-246f46ee7059-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-21 8:05 ` Uwe Kleine-König 2017-03-21 8:05 ` Uwe Kleine-König 2017-03-21 11:53 ` Greg Ungerer 2017-03-21 11:53 ` Greg Ungerer [not found] ` <942cfc4b-445b-ca51-1823-2391cea62abf-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-21 12:11 ` Uwe Kleine-König 2017-03-21 12:11 ` Uwe Kleine-König [not found] ` <20170321121133.jcmhhbszj2d42h3w-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> 2017-03-21 13:22 ` Greg Ungerer 2017-03-21 13:22 ` Greg Ungerer [not found] ` <20678cef-f667-9915-aa00-8877ad152a8c-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-03-21 19:23 ` Uwe Kleine-König 2017-03-21 19:23 ` Uwe Kleine-König 2017-03-21 20:15 ` Geert Uytterhoeven 2017-03-21 20:15 ` Geert Uytterhoeven [not found] ` <CAMuHMdW+KcPCAweneu4pTg1Pb-uAvYGz1+Z=oEDYoOt4gWrjhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2017-03-22 0:50 ` Greg Ungerer 2017-03-22 0:50 ` Greg Ungerer 2017-03-22 7:09 ` Geert Uytterhoeven 2017-03-22 7:09 ` Geert Uytterhoeven 2017-09-04 12:47 ` Applied "spi: imx: fix use of native chip-selects with devicetree" to the spi tree Mark Brown 2017-09-04 12:47 ` Mark Brown 2017-10-10 20:38 ` [2/2] spi: imx: fix use of native chip-selects with devicetree Trent Piepho 2017-10-10 20:38 ` Trent Piepho 2017-10-12 6:26 ` Greg Ungerer 2017-10-12 6:26 ` Greg Ungerer [not found] ` <209bb901-875e-8007-06f8-3ae9698a0e41-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org> 2017-10-12 20:41 ` Trent Piepho 2017-10-12 20:41 ` Trent Piepho 2017-03-20 7:35 ` [PATCH 0/2] spi: imx: native chip selects and devicetree Shawn Guo 2017-03-20 7:35 ` Shawn Guo
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=4a8449d9-cc38-d642-0853-246f46ee7059@linux-m68k.org \ --to=gerg@linux-m68k.org \ --cc=fabio.estevam@nxp.com \ --cc=kernel@pengutronix.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-spi@vger.kernel.org \ --cc=shawnguo@kernel.org \ --cc=vladimir_zapolskiy@mentor.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: linkBe 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.