linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: linux-wireless@vger.kernel.org,
	Helmut Schaa <helmut.schaa@googlemail.com>,
	Gabor Juhos <juhosg@openwrt.org>,
	Serge Vasilugin <vasilugin@yandex.ru>,
	Mathias Kresin <dev@kresin.me>,
	Michel Stempin <michel.stempin@wanadoo.fr>
Subject: Re: [PATCH v4 0/3] rt2x00: RT5350 support
Date: Fri, 20 Jan 2017 16:38:12 +0100	[thread overview]
Message-ID: <20170120153812.GA23737@redhat.com> (raw)
In-Reply-To: <20170120143219.GB22861@makrotopia.org>

Hi

On Fri, Jan 20, 2017 at 03:32:19PM +0100, Daniel Golle wrote:
> On Fri, Jan 20, 2017 at 02:28:23PM +0100, Stanislaw Gruszka wrote:
> > Repost patches from Daniel with updated clock handling and
> > correct author of RT5350 patch.
> > 
> > Note I did not test patches on SOC devices, but getting
> > clock frequency is simple and should be trouble-free.
> 
> Thanks a lot for handling this!
> And big thanks to everyone involved for reviewing a smelly pile of
> patches we had rotting here for half a decade...
> 
> Would you like me to re-work and re-submit the remaining patches needed
> to support RT3883 and RF3853?

Yes, please post them in small sets. 

> Otherwise, the next thing I'd have in mind would be to add device-tree
> bindings to handle in-flash EEPROM loading, see the patches 60[2-9]* in
> https://git.lede-project.org/?p=source.git;a=tree;f=package/kernel/mac80211/patches
> 
> Imho having only support for MTD partitions and skip support for
> requesting firmware files from userspace for now would be the cleanest
> way towards proper WiSoC support in vanilla kernels.
> Obviously our existing patches need to be reworked and stuff needs to
> be added to Documentation/devicetree/bindings.
> Support for non-device-tree legacy platforms which need platform_data
> and legacy EEPROM loading mechanism can remain a local patch in our
> tree until those will no longer be needed.
> Does everybody agree with this general direction?

Sound ok for me.

Thanks
Stanislaw

      reply	other threads:[~2017-01-20 15:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 13:28 [PATCH v4 0/3] rt2x00: RT5350 support Stanislaw Gruszka
2017-01-20 13:28 ` [PATCH v4 1/3] rt2x00: add copy of clk for soc devices Stanislaw Gruszka
2017-01-20 14:13   ` Daniel Golle
2017-01-28  7:09   ` [v4,1/3] " Kalle Valo
2017-01-28 19:39   ` [PATCH v4 1/3] " Felix Fietkau
2017-01-29 11:16     ` Stanislaw Gruszka
2017-01-20 13:28 ` [PATCH v4 2/3] rt2x00: rt2800lib: add support for RT3352 with 20MHz crystal Stanislaw Gruszka
2017-01-20 13:28 ` [PATCH v4 3/3] rt2x00: add support for RT5350 WiSoC Stanislaw Gruszka
2017-01-20 14:32 ` [PATCH v4 0/3] rt2x00: RT5350 support Daniel Golle
2017-01-20 15:38   ` Stanislaw Gruszka [this message]

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=20170120153812.GA23737@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=daniel@makrotopia.org \
    --cc=dev@kresin.me \
    --cc=helmut.schaa@googlemail.com \
    --cc=juhosg@openwrt.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michel.stempin@wanadoo.fr \
    --cc=vasilugin@yandex.ru \
    /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).