All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uri Shkolnik <urishk@yahoo.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Michael Krufky <mkrufky@linuxtv.org>, linux-media@vger.kernel.org
Subject: Re: [PATCH 1/1] siano: add high level SDIO interface driver for SMS based cards
Date: Thu, 12 Mar 2009 07:25:29 -0700 (PDT)	[thread overview]
Message-ID: <541911.18449.qm@web110813.mail.gq1.yahoo.com> (raw)


Mauro and all,

I submitted 3 patches, two modifications for the SDIO generic stack, and one new high level SDIO interface driver for Siano based devices.

This concludes SDIO related changes, with one exception, which is explained below.

However this explanation requires some overview about Siano's module inner architecture.

The Siano kernel module architecture is composed from:
1) SMS "Core" - This main component holds all Siano's host-device protocol logic, and any logic needed to bind the other module's components, interface and adapters.
2) Interfaces drivers (SDIO, USB, TS, SPP, HIF, ...) - At lease one interface driver must be compiled and linked, but multiple interfaces are supported. This feature enables platforms like the Asus UMPC series to use SMS based USB dongle and SMS based SDIO dongle simultaneously. 
3) Client adapters (DVB API v3, DVB API v5, others) - Similar to the interfaces drivers, at least one client adapter must be linked, but multiple are supported.
4) SMS "cards" - This component contains any hardware target specific information (like LEDs locations, antenna configuration, alternative firmware names, and much more), leaving any other component target-independent.


And now back to SDIO....

True all SDIO related sources files are now updated (after these 3 patches), but since the build system (Kconfig & Makefile) and "smscore" component are yet to be updated, the SDIO interface driver can not be linked into the module.
The option to link and use the SDIO interface driver, will be available after those files will be updated (hope it'll happen shortly).


One question: Should I continue submit patches (I have them ready), or should I wait till the 3 previous submission will be reviewed and committed?


Regards,

Uri





      

             reply	other threads:[~2009-03-12 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 14:25 Uri Shkolnik [this message]
2009-03-14 11:07 ` [PATCH 1/1] siano: add high level SDIO interface driver for SMS based cards Mauro Carvalho Chehab
  -- strict thread matches above, loose matches on Subject: below --
2009-03-14 13:20 Uri Shkolnik
2009-03-13  0:49 Uri Shkolnik
2009-03-14 16:37 ` Alexey Klimov
2009-03-12 13:52 Uri Shkolnik
2009-03-12 22:46 ` Alexey Klimov
2009-03-14 10:51 ` Mauro Carvalho Chehab
2009-03-14 11:02   ` Patrick Boettcher
2009-03-14 11:29     ` Mauro Carvalho Chehab
2009-03-14 15:49       ` Patrick Boettcher

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=541911.18449.qm@web110813.mail.gq1.yahoo.com \
    --to=urishk@yahoo.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mkrufky@linuxtv.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.