[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YgE1PD2irQeinD9N@sirena.org.uk>
Date: Mon, 7 Feb 2022 15:05:32 +0000
From: Mark Brown <broonie@...nel.org>
To: Krishna Yarlagadda <kyarlagadda@...dia.com>
Cc: "thierry.reding@...il.com" <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
Sowjanya Komatineni <skomatineni@...dia.com>,
Laxman Dewangan <ldewangan@...dia.com>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"p.zabel@...gutronix.de" <p.zabel@...gutronix.de>
Subject: Re: [PATCH 6/6] spi: tegra210-quad: combined sequence mode
On Mon, Feb 07, 2022 at 02:54:00PM +0000, Krishna Yarlagadda wrote:
> > > + if (cdata->is_cmb_xfer && transfer_count == 3)
> > > + ret = tegra_qspi_combined_seq_xfer(tqspi, msg);
> > > + else
> > > + ret = tegra_qspi_non_combined_seq_xfer(tqspi, msg);
> > This check needs to be more specific. But like I said in reply to the binding
> > patch I don't see why we can't just pattern match on the data without requiring
> > a property here, we'd need to check that the message is suitable no matter
> > what.
> There is no real-world use case we encountered so far preventing us stick to pattern.
> But this was to avoid any corner case where there could be 3 different transfers sent in single msg.
So you'll remove the property and just pattern match on the message?
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists