b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <m@bues.ch>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Larry Finger <larry.finger@lwfinger.net>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	b43-dev <b43-dev@lists.infradead.org>
Subject: [PATCH][RFC][RFT] ssb: pick PCMCIA host code support from b43 driver
Date: Wed, 23 Sep 2015 17:58:01 +0200	[thread overview]
Message-ID: <20150923175801.69076f31@wiggum> (raw)
In-Reply-To: <CACna6rzSqnJF2uBS-DszR+1PFNwqM8S0WecAE+R4QRJjGYuXYQ@mail.gmail.com>

On Wed, 23 Sep 2015 12:02:48 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:

> On 21 September 2015 at 18:20, Michael B?sch <m@bues.ch> wrote:
> > On Mon, 21 Sep 2015 11:04:19 +0200
> > Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> >> @@ -1464,6 +1463,12 @@ static int __init ssb_modinit(void)
> >>               /* don't fail SSB init because of this */
> >>               err = 0;
> >>       }
> >> +     err = ssb_host_pcmcia_init();
> >> +     if (err) {
> >> +             ssb_err("PCMCIA host initialization failed\n");
> >> +             /* don't fail SSB init because of this */
> >
> > Why not? What's the point of not failing here?
> 
> I just copied the logic from few lines above where we handle PCI init.
> I guess the point was to support other host devices even is PCI host
> registration fails.


Ah I misread it. This is at modinit time. That might make sense then.


> >> +static const struct pcmcia_device_id ssb_host_pcmcia_tbl[] = {
> >> +     PCMCIA_DEVICE_MANF_CARD(0x2D0, 0x448),
> >> +     PCMCIA_DEVICE_MANF_CARD(0x2D0, 0x476),
> >> +     PCMCIA_DEVICE_NULL,
> >> +};
> >
> > This doesn't belong into ssb'c pcmcia.c, IMO.
> > It should be in a new file called b43_pcmcia_bridge.c, just like we have
> > b43_pci_bridge.c.
> > The bridge code technically (also for pci) doesn't belong into ssb. But
> > it makes kconfig simpler.
> 
> This is something I don't understand. This PCI bridge was also always
> confusing me.
> Why do we want a separated file for that? What's wrong with having 1
> file for host (PCI/PCMCIA) driver (probe and remove functions) *and*
> ssb initialization?


Because that's not ssb code. These are device IDs for b43 devices.
We just keep it in ssb to make module handling easier.
Ssb also runs non-b43 devices.
Think of it like PCI IDs that belong into the driver and not the PCI
subsystem.

-- 
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20150923/850066a7/attachment.sig>

  reply	other threads:[~2015-09-23 15:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  9:04 [PATCH][RFC][RFT] ssb: pick PCMCIA host code support from b43 driver Rafał Miłecki
2015-09-21 16:14 ` Larry Finger
2015-09-21 16:26   ` Michael Büsch
2015-09-21 16:38     ` Larry Finger
2015-09-21 16:20 ` Michael Büsch
2015-09-23 10:02   ` Rafał Miłecki
2015-09-23 15:58     ` Michael Büsch [this message]
2015-10-14 11:17       ` Rafał Miłecki
2015-10-14 14:48         ` Michael Büsch

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=20150923175801.69076f31@wiggum \
    --to=m@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=hauke@hauke-m.de \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.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).