From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Mark Brown <broonie@kernel.org>, linux-spi@vger.kernel.org
Subject: Re: [PATCH v2 1/2] spi: dw: Make DMA request line assignments explicit for Intel Medfield
Date: Fri, 29 May 2020 21:49:55 +0300 [thread overview]
Message-ID: <20200529184955.GY1634618@smile.fi.intel.com> (raw)
In-Reply-To: <20200529184050.bkn72tash33zgoo4@mobilestation>
On Fri, May 29, 2020 at 09:40:50PM +0300, Serge Semin wrote:
> On Fri, May 29, 2020 at 09:31:49PM +0300, Andy Shevchenko wrote:
> > The 2afccbd283ae ("spi: dw: Discard static DW DMA slave structures")
> > did a clean up of global variables, which is fine, but messed up with
> > the carefully provided information in the custom DMA slave structures.
> > There reader can find an assignment of the DMA request lines in use.
> >
> > Partially revert the above mentioned commit to restore readability
> > and maintainability of the code.
> >
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > v2: rebased against latest spi/for-next
> > drivers/spi/spi-dw-dma.c | 14 ++++++--------
> > 1 file changed, 6 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/spi/spi-dw-dma.c b/drivers/spi/spi-dw-dma.c
> > index 1b96cec6d8cd..53d5257662e8 100644
> > --- a/drivers/spi/spi-dw-dma.c
> > +++ b/drivers/spi/spi-dw-dma.c
> > @@ -61,10 +61,8 @@ static void dw_spi_dma_maxburst_init(struct dw_spi *dws)
> >
> > static int dw_spi_dma_init_mfld(struct device *dev, struct dw_spi *dws)
> > {
> > - struct dw_dma_slave slave = {
> > - .src_id = 0,
> > - .dst_id = 0
> > - };
>
> > + struct dw_dma_slave dma_tx = { .dst_id = 1 }, *tx = &dma_tx;
> > + struct dw_dma_slave dma_rx = { .src_id = 0 }, *rx = &dma_rx;
>
> You know my attitude to these changes.) But anyway what's the point in having
> the *tx and *rx pointers here? Without any harm to the readability you can use
> the structures names directly, don't you?
I will wait for Mark to decide.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-05-29 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 18:31 [PATCH v2 1/2] spi: dw: Make DMA request line assignments explicit for Intel Medfield Andy Shevchenko
2020-05-29 18:31 ` [PATCH v2 2/2] spi: dw: Refactor mid_spi_dma_setup() to separate DMA and IRQ config Andy Shevchenko
2020-05-29 18:40 ` [PATCH v2 1/2] spi: dw: Make DMA request line assignments explicit for Intel Medfield Serge Semin
2020-05-29 18:49 ` Andy Shevchenko [this message]
2020-05-29 19:04 ` Serge Semin
2020-05-29 19:21 ` Andy Shevchenko
2020-05-29 19:52 ` Mark Brown
2020-06-01 12:00 ` Serge Semin
2020-05-29 21:06 ` Mark Brown
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=20200529184955.GY1634618@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=linux-spi@vger.kernel.org \
/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 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.