From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
e1000-devel@lists.sourceforge.net,
Greg Rose <gregory.v.rose@intel.com>,
John Ronciak <john.ronciak@intel.com>,
netdev@vger.kernel.org,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Rasesh Mody <rmody@brocade.com>,
Tushar Dave <tushar.n.dave@intel.com>
Subject: Re: [RFC 0/7] Fixing dma mask setting in various network drivers
Date: Mon, 17 Jun 2013 21:45:05 +0100 [thread overview]
Message-ID: <20130617204505.GT2718@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1371501341.2133.130.camel@jtkirshe-mobl>
On Mon, Jun 17, 2013 at 01:35:41PM -0700, Jeff Kirsher wrote:
> On Mon, 2013-06-17 at 15:01 +0100, Russell King - ARM Linux wrote:
> > On Tue, Jun 11, 2013 at 11:12:30AM -0700, Jesse Brandeburg wrote:
> > > This is my proposed change to the intel drivers. Comments?
> > >
> > > + if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(64))) {
> > > + pci_using_dac = true;
> > > + /* coherent mask for the same size will always succeed if
> > > + * dma_set_mask does
> > > + */
> > > + dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(64));
> > > + } else if (!dma_set_mask(&pdev->dev, DMA_BIT_MASK(32))) {
> > > + pci_using_dac = false;
> > > + dma_set_coherent_mask(&pdev->dev, DMA_BIT_MASK(32));
> > > + } else {
> > > + dev_err(&pdev->dev, "%s: DMA configuration failed: %d\n",
> > > + __func__, err);
> > > + err = -EIO;
> > > + goto err_dma;
> > > }
> > >
> >
> > So, will you be going with this change rather than mine, which apparantly
> > Jeff queued? Please let me know what you decide so I can keep my private
> > git tree in sync with what you've decided to avoid conflicting with
> > further dma-mask changes which I'm working on.
> >
> > Thanks.
>
> I thought the kernel helper function dma_set_mask_and_coherent(...) was
> the best solution.
>
> I dropped your original series of patches from my queue since it
> appeared that there was a better alternative to this solution.
Such a helper doesn't exist yet, and I'm not sure these changes should
wait for that. Hmm, okay, it's probably too late in the -rc cycle
anyway for these changes now.
I'll respin them according to Jesse's patch above, but as I have already
mentioned, this will be part of a much larger series, and I was hoping
to get those trivial fixes in for 3.10 to avoid that kind of dependency.
Instead, they'll be stuck at the bottom of a much larger series, which
will depend on these changes. Bah.
prev parent reply other threads:[~2013-06-17 20:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 23:08 [RFC 0/7] Fixing dma mask setting in various network drivers Russell King - ARM Linux
2013-06-10 23:09 ` [PATCH 1/7] NET: brocade/bna/bnad.c: fix 32-bit DMA mask handling Russell King
2013-06-10 23:10 ` [PATCH 2/7] NET: intel/e1000e/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:11 ` [PATCH 3/7] NET: intel/igb/igb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:12 ` [PATCH 4/7] NET: intel/igbvf/netdev.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:13 ` [PATCH 5/7] NET: intel/ixgb/ixgb_main.c: " Russell King
2013-06-10 23:27 ` Jeff Kirsher
2013-06-10 23:14 ` [PATCH 6/7] NET: intel/ixgbe/ixgbe_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-10 23:15 ` [PATCH 7/7] NET: intel/ixgbevf/ixgbevf_main.c: " Russell King
2013-06-10 23:28 ` Jeff Kirsher
2013-06-11 18:12 ` [RFC 0/7] Fixing dma mask setting in various network drivers Jesse Brandeburg
2013-06-11 20:35 ` Russell King - ARM Linux
2013-06-11 23:50 ` Jesse Brandeburg
2013-06-12 0:01 ` Russell King - ARM Linux
2013-06-17 14:01 ` Russell King - ARM Linux
2013-06-17 20:35 ` Jeff Kirsher
2013-06-17 20:45 ` Russell King - ARM Linux [this message]
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=20130617204505.GT2718@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=rmody@brocade.com \
--cc=tushar.n.dave@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).