From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] [PATCH] pinctrl: sun4i: add spdif to pin description.
Date: Wed, 12 Aug 2015 10:34:37 +0200 [thread overview]
Message-ID: <55CB051D.3090109@redhat.com> (raw)
In-Reply-To: <CAEKpxBmS6YJMjREc3gmeSQOzBXFKw=Sb-xPK57oUn6BtmASErg@mail.gmail.com>
Hi,
On 12-08-15 07:31, Code Kipper wrote:
> On 11 August 2015 at 18:48, Chen-Yu Tsai <wens@csie.org> wrote:
>
>> On Wed, Aug 12, 2015 at 12:19 AM, <codekipper@gmail.com> wrote:
>>> From: Marcus Cooper <codekipper@gmail.com>
>>>
>>> Signed-off-by: Marcus Cooper <codekipper@gmail.com>
>>> ---
>>> drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c | 9 ++++++---
>>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c
>> b/drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c
>>> index 7376a97..daf7dec 100644
>>> --- a/drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c
>>> +++ b/drivers/pinctrl/sunxi/pinctrl-sun4i-a10.c
>>> @@ -135,7 +135,8 @@ static const struct sunxi_desc_pin sun4i_a10_pins[]
>> = {
>>> SUNXI_PIN(SUNXI_PINCTRL_PIN(B, 3),
>>> SUNXI_FUNCTION(0x0, "gpio_in"),
>>> SUNXI_FUNCTION(0x1, "gpio_out"),
>>> - SUNXI_FUNCTION(0x2, "ir0")), /* TX */
>>> + SUNXI_FUNCTION(0x2, "ir0"), /* TX */
>>> + SUNXI_FUNCTION(0x4, "spdif")), /* MCLK */
>>> SUNXI_PIN(SUNXI_PINCTRL_PIN(B, 4),
>>> SUNXI_FUNCTION(0x0, "gpio_in"),
>>> SUNXI_FUNCTION(0x1, "gpio_out"),
>>> @@ -176,11 +177,13 @@ static const struct sunxi_desc_pin
>> sun4i_a10_pins[] = {
>>> SUNXI_FUNCTION(0x0, "gpio_in"),
>>> SUNXI_FUNCTION(0x1, "gpio_out"),
>>> SUNXI_FUNCTION(0x2, "i2s"), /* DI */
>>> - SUNXI_FUNCTION(0x3, "ac97")), /* DI */
>>> + SUNXI_FUNCTION(0x3, "ac97"), /* DI */
>>> + SUNXI_FUNCTION(0x4, "spdif")), /* DI */
>>> SUNXI_PIN(SUNXI_PINCTRL_PIN(B, 13),
>>> SUNXI_FUNCTION(0x0, "gpio_in"),
>>> SUNXI_FUNCTION(0x1, "gpio_out"),
>>> - SUNXI_FUNCTION(0x2, "spi2")), /* CS1 */
>>> + SUNXI_FUNCTION(0x2, "spi2"), /* CS1 */
>>> + SUNXI_FUNCTION(0x4, "spdif")), /* DO */
>>
>> The datasheet and manual list them as NC or Reserved. Maybe mention how
>> you knew
>> they were available?
>>
> Not sure if this deserves to be in the commit message but I can definitely
> put together a covering letter with links etc.
I dear to say it belongs right there in the source code, use a multi-line
comment above the SUNXI_FUNCTION(0x4, "spdif")) to explain where the mux
info comes from. someday sooner or later someone is going to compare the
kernel mux table to the datasheet and think "huh, that is not right",
that person will be saved an immense amount of time by simply having a
comment there.
And do NOT say that this will not happen, because I've already done
such a comparison once in the past.
Regards,
Hans
next prev parent reply other threads:[~2015-08-12 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 16:19 [PATCH] pinctrl: sun4i: add spdif to pin description codekipper at gmail.com
2015-08-11 16:48 ` [linux-sunxi] " Chen-Yu Tsai
[not found] ` <CAEKpxBmS6YJMjREc3gmeSQOzBXFKw=Sb-xPK57oUn6BtmASErg@mail.gmail.com>
2015-08-12 8:34 ` Hans de Goede [this message]
[not found] ` <CAEKpxB=UQYEnwXYAzMZA4noR9Xg8wnSjD+H0bNO5GV3dtZQtTg@mail.gmail.com>
2015-08-12 9:18 ` Chen-Yu Tsai
2015-08-12 10:18 ` Hans de Goede
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=55CB051D.3090109@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@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.