From: Christoph Hellwig <hch@lst.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Christoph Hellwig <hch@lst.de>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/4] ARM/dma-mapping: don't handle NULL devices in dma-direct.h
Date: Fri, 18 Sep 2020 07:10:30 +0200 [thread overview]
Message-ID: <20200918051030.GA21261@lst.de> (raw)
In-Reply-To: <20200917185009.GB1559@shell.armlinux.org.uk>
On Thu, Sep 17, 2020 at 07:50:10PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Sep 17, 2020 at 07:32:28PM +0200, Christoph Hellwig wrote:
> > The DMA API removed support for not passing in a device a long time
> > ago, so remove the NULL checks.
>
> What happens with ISA devices?
For actual drivers they've been switched to struct isa_driver, which
provides a struct device. For some of the special case like the
arch/arm/kernel/dma-isa.c we now use static struct device instances.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-omap@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM/dma-mapping: don't handle NULL devices in dma-direct.h
Date: Fri, 18 Sep 2020 07:10:30 +0200 [thread overview]
Message-ID: <20200918051030.GA21261@lst.de> (raw)
In-Reply-To: <20200917185009.GB1559@shell.armlinux.org.uk>
On Thu, Sep 17, 2020 at 07:50:10PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Sep 17, 2020 at 07:32:28PM +0200, Christoph Hellwig wrote:
> > The DMA API removed support for not passing in a device a long time
> > ago, so remove the NULL checks.
>
> What happens with ISA devices?
For actual drivers they've been switched to struct isa_driver, which
provides a struct device. For some of the special case like the
arch/arm/kernel/dma-isa.c we now use static struct device instances.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, linux-omap@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
Christoph Hellwig <hch@lst.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM/dma-mapping: don't handle NULL devices in dma-direct.h
Date: Fri, 18 Sep 2020 07:10:30 +0200 [thread overview]
Message-ID: <20200918051030.GA21261@lst.de> (raw)
In-Reply-To: <20200917185009.GB1559@shell.armlinux.org.uk>
On Thu, Sep 17, 2020 at 07:50:10PM +0100, Russell King - ARM Linux admin wrote:
> On Thu, Sep 17, 2020 at 07:32:28PM +0200, Christoph Hellwig wrote:
> > The DMA API removed support for not passing in a device a long time
> > ago, so remove the NULL checks.
>
> What happens with ISA devices?
For actual drivers they've been switched to struct isa_driver, which
provides a struct device. For some of the special case like the
arch/arm/kernel/dma-isa.c we now use static struct device instances.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-18 5:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 17:32 RFC: remove the need for <asm/dma-direct.h> on ARM Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` [PATCH 1/4] ARM/omap1: switch to use dma_direct_set_offset for lbus DMA offsets Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-18 5:49 ` Tony Lindgren
2020-09-18 5:49 ` Tony Lindgren
2020-09-18 5:49 ` Tony Lindgren
2020-09-19 22:29 ` Janusz Krzysztofik
2020-09-19 22:29 ` Janusz Krzysztofik
2020-09-19 22:29 ` Janusz Krzysztofik
2020-09-21 6:44 ` Tony Lindgren
2020-09-21 6:44 ` Tony Lindgren
2020-09-21 6:44 ` Tony Lindgren
2020-09-21 6:47 ` Christoph Hellwig
2020-09-21 6:47 ` Christoph Hellwig
2020-09-21 6:47 ` Christoph Hellwig
2020-09-23 10:05 ` Russell King - ARM Linux admin
2020-09-23 10:05 ` Russell King - ARM Linux admin
2020-09-23 10:05 ` Russell King - ARM Linux admin
2020-09-25 4:16 ` Christoph Hellwig
2020-09-25 4:16 ` Christoph Hellwig
2020-09-25 4:16 ` Christoph Hellwig
2020-09-17 17:32 ` [PATCH 2/4] ARM/footbridge: " Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 18:53 ` Russell King - ARM Linux admin
2020-09-17 18:53 ` Russell King - ARM Linux admin
2020-09-17 18:53 ` Russell King - ARM Linux admin
2020-09-17 17:32 ` [PATCH 3/4] ARM/dma-mapping: don't handle NULL devices in dma-direct.h Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 18:50 ` Russell King - ARM Linux admin
2020-09-17 18:50 ` Russell King - ARM Linux admin
2020-09-17 18:50 ` Russell King - ARM Linux admin
2020-09-18 5:10 ` Christoph Hellwig [this message]
2020-09-18 5:10 ` Christoph Hellwig
2020-09-18 5:10 ` Christoph Hellwig
2020-09-17 17:32 ` [PATCH 4/4] ARM/dma-mapping: remove the arm specific phys to dma translation helpers Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
2020-09-17 17:32 ` Christoph Hellwig
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=20200918051030.GA21261@lst.de \
--to=hch@lst.de \
--cc=aaro.koskinen@iki.fi \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robin.murphy@arm.com \
--cc=tony@atomide.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: 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.