All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Harsha Rao <harshrao464@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: Support on vendor id and device id
Date: Tue, 27 Feb 2018 12:15:10 +0100	[thread overview]
Message-ID: <5A953DBE.9070805@broadcom.com> (raw)
In-Reply-To: <CAPcv9S3wyPd5jD1PZWtDf-mRicmzRmz00qh5Jbov_N_egBAEZg@mail.gmail.com>

On 2/27/2018 11:16 AM, Harsha Rao wrote:
> Hi folks,
> I am developing a new wifi driver for our sdio based wifi device.
>
> I see that SDIO_VENDOR_ID and SDIO_DEVICE_ID for our device (We had
> bought the SDIO IP from 3rd party)  is already  been used by some
> other vendor and its already into staging .
>
> Please suggest me how can I move forward to submit the driver for staging.

Can you be more specific about the conflicting vendor id and device id?

> Is there a way to reconfigure the values in the SDIO host for
> different value or does Linux allow two drivers with same values to
> survive mutual exclusively

First come first serve. When a device is detected, the driver core looks 
for drivers supporting it based on device table and the first that 
successfully returns from the .probe() callback is bound to the device.

Regards,
Arend

  reply	other threads:[~2018-02-27 11:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-27 10:16 Support on vendor id and device id Harsha Rao
2018-02-27 11:15 ` Arend van Spriel [this message]
2018-02-27 13:30   ` Harsha Rao
2018-02-27 15:14     ` Larry Finger
2018-02-27 15:29       ` Harsha Rao
2018-02-27 17:15         ` Steve deRosier
2018-02-27 17:34           ` Steve deRosier
2018-02-27 20:04             ` Arend van Spriel
2018-02-27 23:14               ` Harsha Rao
2018-02-28  9:38                 ` Arend van Spriel
2018-03-01 10:10                   ` Harsha Rao
2018-03-13 19:23                     ` Arend van Spriel

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=5A953DBE.9070805@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=harshrao464@gmail.com \
    --cc=linux-wireless@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.