From: Ajay Singh <ajay.kathat@microchip.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: <devel@driverdev.osuosl.org>, <gregkh@linuxfoundation.org>,
<linux-wireless@vger.kernel.org>, <nicolas.ferre@microchip.com>,
<ganesh.krishna@microchip.com>, <adham.abozaeid@microchip.com>,
<aditya.shankar@microchip.com>
Subject: Re: feedback on mainlining wilc1000 staging driver
Date: Fri, 17 Aug 2018 10:02:33 +0530 [thread overview]
Message-ID: <20180817100233.7f1c00d9@ajaysk-VirtualBox> (raw)
In-Reply-To: <87o9e2twe9.fsf@purkki.adurom.net>
On Thu, 16 Aug 2018 13:53:50 +0300
Kalle Valo <kvalo@codeaurora.org> wrote:
> Kalle Valo <kvalo@codeaurora.org> writes:
>
> > Ajay Singh <ajay.kathat@microchip.com> writes:
> >
> >> Hi Greg,
> >>
> >> We all are working on submitting and reviewing patches for
> >> wilc1000 in staging driver for quite some time.
> >>
> >> We would like to have feedback on the next steps to bring wilc1000
> >> driver closer to move into the wireless subsystem tree.
> >>
> >> In summary, the following major things from TODO have been
> >> addressed in staging:
> >> -remove the defined feature as kernel versions
> >> -remove OS wrapper functions
> >> -remove custom debug and tracing functions
> >> -rework comments and function headers(also coding style)
> >> -remove build warnings
> >> -replace all semaphores with mutexes or completions
> >> -make spi and sdio components coexist in one build
> >> -turn compile-time platform configuration (BEAGLE_BOARD,
> >> PANDA_BOARD, PLAT_WMS8304, PLAT_RKXXXX, CUSTOMER_PLATFORM, ...)
> >> into run-time options that are read from DT
> >> -replace SIOCDEVPRIVATE commands with generic API functions
> >> -use wext-core handling instead of private SIOCSIWPRIV
> >> implementation
> >
> > From wireless point of view: if I see wext mentioned anywhere in the
> > driver I stop right there. cfg80211 is a hard requirement for us
> > nowadays.
>
> Clarification: Depending on the hardware design either cfg80211 or
> mac80211 is a hard requirement. I haven't checked wilc1000 at all so I
> don't know what design it has but if it's a "softmac" design then it
> has to use mac80211, we do not want to support multiple 802.11 UMAC
> stacks.
>
The TODO item to make use of wext-core is obsolete. Previously wilc1000
driver also had few wext ioctl use but now it’s completely removed and
cfg80211 operation callbacks are used.
wilc1000 driver make use of cfg80211 and isn’t a "softmac".
We need help to review and identify if there are any pending items
for wilc1000 driver, so we can address those issues and make it ready
to move to the wireless subsystem.
Regards,
Ajay
next prev parent reply other threads:[~2018-08-17 7:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 20:22 feedback on mainlining wilc1000 staging driver Ajay Singh
2018-08-16 6:43 ` Greg KH
2018-08-15 20:53 ` Ajay Singh
2018-08-16 10:47 ` Kalle Valo
2018-08-16 10:53 ` Kalle Valo
2018-08-17 4:32 ` Ajay Singh [this message]
2018-08-17 7:49 ` Kalle Valo
2018-08-17 8:21 ` Arend van Spriel
2018-08-17 8:36 ` Kalle Valo
2018-08-17 9:09 ` Ajay Singh
2018-08-23 11:07 ` Kalle Valo
2018-09-26 10:27 ` Ajay Singh
2018-10-04 12:27 ` Kalle Valo
2018-10-05 2:33 ` Ajay Singh
2018-10-05 5:16 ` Kalle Valo
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=20180817100233.7f1c00d9@ajaysk-VirtualBox \
--to=ajay.kathat@microchip.com \
--cc=adham.abozaeid@microchip.com \
--cc=aditya.shankar@microchip.com \
--cc=devel@driverdev.osuosl.org \
--cc=ganesh.krishna@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nicolas.ferre@microchip.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).