From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] dmaengine: shdma: use normal interface for passing slave id
Date: Tue, 20 Jan 2015 00:54:44 +0000 [thread overview]
Message-ID: <9373136.Tcmkvq4FcA@avalon> (raw)
In-Reply-To: <87oapzxxzw.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
On Tuesday 20 January 2015 00:37:04 Kuninori Morimoto wrote:
> Hi Laurent
>
> >> The shmobile platform is one of only two users of the slave_id field
> >> in dma_slave_config, which is incompatible with the way that the
> >> dmaengine API normally works.
> >>
> >> I've had a closer look at the existing code now and found that all
> >> slave drivers that pass a slave_id in dma_slave_config for SH do that
> >> right after passing the same ID into shdma_chan_filter, so we can just
> >> rely on that. However, the various shdma drivers currently do not
> >> remember the slave ID that was passed into the filter function when
> >> used in non-DT mode and only check the value to find a matching channel,
> >> unlike all other drivers.
> >>
> >> There might still be drivers that are not part of the kernel that rely
> >> on setting the slave_id to some other value, so to be on the safe side,
> >> this adds another 'real_slave_id' field to shdma_chan that remembers
> >> the ID and uses it when a driver passes a zero slave_id in
> >> dma_slave_config, like most drivers do.
> >>
> >> Eventually, the real_slave_id and slave_id fields should just get merged
> >> into one field, but that requires other changes.
> >
> > Morimoto-san, do you think we need to care about out-of-tree drivers here,
> > or could we merge slave_id and real_slave_id already ?
>
> Sorry, what does your "out-of-tree" mean ?
That's the drivers that are not part of the kernel that Arnd mentioned in this
commit message.
> > > drivers/dma/sh/shdma-base.c | 72 +++++++++++++++++++++---------
> > > drivers/mmc/host/sh_mmcif.c | 12 +++----
> > > drivers/mmc/host/sh_mobile_sdhi.c | 2 --
> > > drivers/mmc/host/tmio_mmc.h | 2 --
> > > drivers/mmc/host/tmio_mmc_dma.c | 4 ---
> > > drivers/mtd/nand/sh_flctl.c | 2 --
> > > drivers/spi/spi-rspi.c | 1 -
> > > drivers/spi/spi-sh-msiof.c | 1 -
> > > include/linux/shdma-base.h | 1 +
> >
> > This might need to be split into different patches to avoid conflicts when
> > merging.
>
> OK, will try in v2
If you can get the various maintainers involved in this to agree on a single
tree through which to merge the patch there will be no need to split it, but
as 3 subsystems are involved it might be difficult to avoid merge conflicts.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-01-20 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 2:24 [PATCH] dmaengine: shdma: use normal interface for passing slave id Kuninori Morimoto
2015-01-19 1:28 ` Laurent Pinchart
2015-01-20 0:37 ` Kuninori Morimoto
2015-01-20 0:54 ` Laurent Pinchart [this message]
2015-01-20 1:18 ` Kuninori Morimoto
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=9373136.Tcmkvq4FcA@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox