From: patchwork-bot+linux-amlogic@kernel.org
To: Hyeonki Hong <hhk7734@gmail.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] [v2] pinctrl: meson: fix drive strength register and bit calculation
Date: Mon, 17 Aug 2020 17:48:51 +0000 [thread overview]
Message-ID: <159768653144.32160.10350237872763117083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200618025916.GA19368@home-desktop>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Thu, 18 Jun 2020 11:59:22 +0900 you wrote:
> If a GPIO bank has greater than 16 pins, PAD_DS_REG is split into two
> or more registers. However, when register and bit were calculated, the
> first register defined in the bank was used, and the bit was calculated
> based on the first pin. This causes problems in setting the driving
> strength.
>
> The following method was used to solve this problem:
> A bit is calculated first using predefined strides. Then, If the bit is
> 32 or more, the register is changed by the quotient of the bit divided
> by 32. And the bit is set to the remainder.
>
> [...]
Here is a summary with links:
- [v2] pinctrl: meson: fix drive strength register and bit calculation
https://git.kernel.org/khilman/linux-amlogic/c/f088ab6d4f4ce49d422c220074b7e605f54e2299
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-08-17 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 2:59 [PATCH] [v2] pinctrl: meson: fix drive strength register and bit calculation Hyeonki Hong
2020-06-18 2:59 ` Hyeonki Hong
2020-06-18 2:59 ` Hyeonki Hong
2020-07-07 11:15 ` Linus Walleij
2020-07-07 11:15 ` Linus Walleij
2020-07-07 11:15 ` Linus Walleij
2020-08-17 17:48 ` patchwork-bot+linux-amlogic [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=159768653144.32160.10350237872763117083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=hhk7734@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.