linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Lin <dlin@marvell.com>,
	"quozl@laptop.org" <quozl@laptop.org>,
	Dan Williams <dcbw@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Chor Teck Law <ctlaw@marvell.com>, Pete Hsieh <peteh@marvell.com>
Subject: Re: [PATCH v4] Add new mac80211 driver mwlwifi.
Date: Wed, 01 Jul 2015 16:57:06 +0200	[thread overview]
Message-ID: <1435762626.2168.1.camel@sipsolutions.net> (raw)
In-Reply-To: <019032ba6cc14a4293b670496dd2bb1e@SC-EXCH02.marvell.com>

On Wed, 2015-07-01 at 14:42 +0000, David Lin wrote:
> > We can leave both selectable by developer testing as per your
> suggestion, and assume users/integrators will know how to put the 
> driver they want in their system. We were warned about causing 
> confusion hence the conditioning in CONFIG. Do you feel there's no 
> concern leaving both driver in, not checking each other's presence? 
> We can comply either way.

I think you should just leave both selectable.

> > > > This looks OK, though I get a very strange dependency loop 
> > > > warning
> > > > from Kconfig here.
> 
> For the next patch, we will modify the code to still work even though 
> the target does not support DTS. So we can remove "select OF" from 
> Kconfig file.

If the driver needs OF don't bother - the dependency loop is very long
and the warning is rather strange.

> > > > > writew(0x00, (void __iomem *)&priv->pcmd_buf[1]);
> > > > 
> > > > cannot be right. This memory isn't __iomem, it's 
> > > > dma_alloc_coherent,
> > > > so a simple write should be done.
> > > > 
> 
> Without this casting, C=2 will cause a warning message like this: 
> "Warning: incorrect type in argument 2 (different address spaces)"

Yes, but the warning is correct and the cast is wrong. This isn't
__iomem, it's simply mapped, so you should just do a
	(u32 *)pcmd_buf[1] = 0;

or something like that. The writev() to such a pointer cannot be right.

> johannes

  reply	other threads:[~2015-07-01 14:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  1:49 [PATCH v4] Add new mac80211 driver mwlwifi David Lin
2015-06-30  3:16 ` Joe Perches
2015-06-30  3:49   ` David Lin
2015-06-30  8:21 ` Johannes Berg
2015-06-30 14:18   ` Dan Williams
2015-06-30 22:26     ` James Cameron
2015-07-01 14:42       ` David Lin
2015-07-01 14:57         ` Johannes Berg [this message]
2015-07-01 23:23           ` David Lin

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=1435762626.2168.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=ctlaw@marvell.com \
    --cc=dcbw@redhat.com \
    --cc=dlin@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=peteh@marvell.com \
    --cc=quozl@laptop.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;
as well as URLs for NNTP newsgroup(s).