[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CP=wtJ5ZScyb0NrRMW0FR0FAGVKRFq9JpFcAoZppn_bA@mail.gmail.com>
Date: Tue, 25 Aug 2020 14:16:05 -0300
From: Fabio Estevam <festevam@...il.com>
To: Matthias Schiffer <matthias.schiffer@...tq-group.com>
Cc: Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: (EXT) Re: (EXT) Re: [PATCH 2/2] ARM: dts: imx6qdl: tqma6: minor fixes
On Tue, Aug 25, 2020 at 11:40 AM Matthias Schiffer
<matthias.schiffer@...tq-group.com> wrote:
> Makes sense. Does the following logic sound correct?
>
> - If num-cs is set, use that (and add it to the docs)
I would not add num-cs to the docs. As far as I can see there is no
imx dts that uses num-cs currently.
> - If num-cs is unset, use the number of cs-gpios
> - If num-cs is unset and no cs-gpios are defined, use a driver-provided
> default
>
>
> I'm not sure if 3 is a particularly useful default either, but it seems
> it was chosen to accommodate boards that previously set this via
> platform data. All SoCs I've checked (i.MX6Q/DL, i.MX6UL, i.MX7) have 4
> internal CS pins per ECSPI instance, so maybe the driver should use
> that as its default instead?
I think it is time to get rid of i.MX board files. I will try to work
on this when I have a chance.
bout using 4 as default chip select number, please also check some
older SoCs like imx25, imx35, imx51, imx53, etc
Powered by blists - more mailing lists