From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Stefan Wahren <wahrenst@gmx.net>,
Linus Walleij <linus.walleij@linaro.org>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH V3 2/2] pinctrl: bcm2835: Implement bcm2711_pinconf_get
Date: Mon, 4 Mar 2024 09:41:31 -0800 [thread overview]
Message-ID: <0e7b891b-8fca-4127-a101-dfa34a0c984a@broadcom.com> (raw)
In-Reply-To: <20240303140137.157522-3-wahrenst@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
On 3/3/24 06:01, Stefan Wahren wrote:
> The BCM2711 allows to read the bias config. So implement pin_conf_get
> accordingly. The pull resistor values has been taken from the
> BCM2711/7211 datasheet.
>
> This implementation assumes that BCM7211 behaves the same way.
>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
Tested-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2024-03-04 17:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 14:01 [PATCH V3 0/2] pinctrl: bcm2835: Implement pin_conf_get Stefan Wahren
2024-03-03 14:01 ` [PATCH V3 1/2] pinctrl: bcm2835: Implement bcm2835_pinconf_get Stefan Wahren
2024-03-03 14:19 ` Chen-Yu Tsai
2024-03-05 22:38 ` Linus Walleij
2024-03-06 3:10 ` Chen-Yu Tsai
2024-03-06 8:38 ` Linus Walleij
2024-03-06 8:55 ` Chen-Yu Tsai
2024-03-06 12:57 ` Linus Walleij
2024-03-06 13:40 ` Chen-Yu Tsai
2024-03-06 17:03 ` Stefan Wahren
2024-03-06 17:07 ` Chen-Yu Tsai
2024-03-06 18:08 ` Stefan Wahren
2024-03-03 14:01 ` [PATCH V3 2/2] pinctrl: bcm2835: Implement bcm2711_pinconf_get Stefan Wahren
2024-03-04 17:41 ` Florian Fainelli [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=0e7b891b-8fca-4127-a101-dfa34a0c984a@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=wahrenst@gmx.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