From: "Heiko Stübner" <heiko@sntech.de>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: linux-rockchip@lists.infradead.org, linux-mmc@vger.kernel.org,
dianders@chromium.org, romain.perier@gmail.com,
FUKAUMI Naoki <naobsd@gmail.com>
Subject: Re: [RFC PATCH] ARM: dts: rockchip: Add wifi support for firefly
Date: Sun, 09 Aug 2015 21:17:15 +0200 [thread overview]
Message-ID: <4932422.vgAJTm4MIh@diego> (raw)
In-Reply-To: <20150809082640.GA5459@panicking>
Hi Michael,
Am Sonntag, 9. August 2015, 10:26:44 schrieb Michael Trimarchi:
[...]
> > > num-slots = <1>;
> > > pinctrl-names = "default";
> > >
> > > - pinctrl-0 = <&sdio0_bus4>, <&sdio0_cmd>, <&sdio0_clk>;
> > > - vmmc-supply = <&vcc_18>;
> > > + pinctrl-0 = <&sdio0_bus4>, <&sdio0_cmd>, <&sdio0_clk>, <&sdio0_int>;
> > > +
> > > + sd-uhs-sdr50;
> > > + sd-uhs-sdr104;
> > > + sd-uhs-ddr50;
> >
> > we don't have mmc tuning capabilities yet, so please no sd-uhs-* stuff.
> > That way you should also be able to leave out the clock-freq-min-max
> > above, as regular "highspeed" does not venture above the 50MHz limit.
>
> Ok, I have tested without it too and it works with a small hack on the code.
> Agree with you
what was this supposed to fix? And what "hack" do you use now?
> > > + cap-sdio-irq;
> > > +
> > > + vmmc-supply = <&vcc_wifi>;
> >
> > the original supply is actually wrong in the dts. vcc_18 is the io voltage
> > used on the
> > pins _to_ the card, not to supply the card itself. So vcc_18 is actually
> > the so called vqmmc-supply.
> > vmmc-supply is done regularly from vcc_io. So your voltage hack above can
> > go away too.
> >
> > Bringup should also use a mmc-power-sequency so you can make sure the
> > rtc_clock is running, which is also needed by the wifi module.
>
> Hack is used to because when sdio subsystem compare the wifi voltage
> capability returned by a specific message on the bus with the possible
> voltage levels that hardware connection provides and take the minimal. The
> card return to support from 2V up and this is the reason to declare it at
> 2V. I will retest again
after the supplies are corrected (see vmmc and vqmmc in the patches) the
supply for the modules should actually be read as the 3.3V that are supplying
it (from vcc_io ... which is called vbat_wl in the schematics).
> > > status = "okay";
> >
> > missing #address-cells and #size-cells values for the subnodes
>
> Correct
>
> > > +
> > > + brcmf: bcrmf@0 {
> > > + compatible = "brcm,bcm4329-fmac";
> > > + interrupt-parent = <&gpio4>;
> > > + reg = <0>;
> > > + interrupts = <30 IRQ_TYPE_EDGE_FALLING>;
> > > + interrupt-names = "host-wake";
> > > + status = "okay";
> > > + };
> > >
> > > };
> > >
> > > &sdmmc {
> >
> > I took the liberty to move stuff around how it should look like, but did
> > not find the time to actually test this. So maybe you can take a look at
> > the attached patches.
>
> Perfect, I will retest as soon as I can and go back to you. Right now
> I have two hardware design around firefly that use the wifi
great
Heiko
next prev parent reply other threads:[~2015-08-09 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 14:12 [RFC PATCH] ARM: dts: rockchip: Add wifi support for firefly Michael Trimarchi
2015-08-08 21:05 ` Heiko Stübner
2015-08-09 8:26 ` Michael Trimarchi
2015-08-09 19:17 ` Heiko Stübner [this message]
2015-11-16 7:39 ` Michael Trimarchi
2015-12-31 12:29 ` Michael Trimarchi
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=4932422.vgAJTm4MIh@diego \
--to=heiko@sntech.de \
--cc=dianders@chromium.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=naobsd@gmail.com \
--cc=romain.perier@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).