linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: dts: ux500: Fix BT+WLAN on Samsung phones
Date: Wed, 17 Mar 2021 16:53:58 +0100	[thread overview]
Message-ID: <CACRpkdYotLSF0+3qPH=isLxFuVcJLQDstuzeW41q=gtF3HV6jA@mail.gmail.com> (raw)
In-Reply-To: <YFIfs5XNDlk0iPr+@gerhold.net>

On Wed, Mar 17, 2021 at 4:28 PM Stephan Gerhold <stephan@gerhold.net> wrote:

> According to the schematics for samsung-golden:
>   - GPIO215 goes to WL_REG_ON of BCM4334
>   - GPIO222 goes to BT_REG_ON of BCM4334

Yes it appears you are right...

This is in conflict with the source code in the vendor tree:
board-golden-pins.c:

        GPIO215_GPIO            | PIN_OUTPUT_LOW,       /* WLAN_RST_N */
        GPIO222_GPIO            | PIN_OUTPUT_LOW,       /* BT_VREG_EN */

However the BCM4334 does not have appear to have
any signal named WLAN_RST_N.

So I suspect a copy/paste error from Janice, which might
need this because of differences between BCM4330 and
BCM4334.

However another part of the patch is still needed because
GPIO215 is default initilized as low:

                wlan_en_default: wlan_en_default {
                        golden_cfg1 {
                                pins = "GPIO215_AH13";  /* WLAN_EN */
                                ste,config = <&gpio_out_lo>;
                        };
                };

It needs to be high, or the SDIO will not enumerate unless
someone powers on the Bluetooth by chance. (The driver
probes after the SDIO card is detected ... catch 22.)

Also IMO GPIO 222 should be modeled as a regulator and
not assigned to "shutdown-gpios", which could be a separate
patch. The whole notion of "shutdown-gpios" seems backward
as the driver handles regulators just fine.

I'll rehash and compare the BCM4330 and BCM4334
datasheets.

Thanks!
Linus Walleij

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-03-17 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 11:07 [PATCH v2] ARM: dts: ux500: Fix BT+WLAN on Samsung phones Linus Walleij
2021-03-17 15:27 ` Stephan Gerhold
2021-03-17 15:53   ` Linus Walleij [this message]
2021-03-17 16:16     ` Stephan Gerhold
2021-03-17 23:32       ` Linus Walleij

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='CACRpkdYotLSF0+3qPH=isLxFuVcJLQDstuzeW41q=gtF3HV6jA@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=stephan@gerhold.net \
    /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).