From: Tomasz Figa <tomasz.figa@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Tomasz Figa <t.figa@samsung.com>
Cc: linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Kukjin Kim <kgene.kim@samsung.com>,
Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH 6/6] pinctrl: samsung: Allow pin value to be initialized using pinfunc
Date: Wed, 09 Jul 2014 10:07:22 +0200 [thread overview]
Message-ID: <53BCF83A.5000403@gmail.com> (raw)
In-Reply-To: <CACRpkdbZXNCHWOK0J2BCKoZN723FwosZQEa2wQHW4KpqX9EvrQ@mail.gmail.com>
On 09.07.2014 09:35, Linus Walleij wrote:
> On Wed, Jul 2, 2014 at 5:41 PM, Tomasz Figa <t.figa@samsung.com> wrote:
>
>> This patch extends the range of settings configurable via pinfunc API
>> to cover pin value as well. This allows configuration of default values
>> of pins, which is useful for pins that are not supposed to be used by
>> any dedicated driver, but need certain board-specific setting.
>>
>> Signed-off-by: Tomasz Figa <t.figa@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> Patch applied.
Thanks!
> It always makes me a little bit sad that we didn't get
> generic pin config in place before this driver but now we have to live
> with it.
That's true. :(
Best regards,
Tomasz
WARNING: multiple messages have this Message-ID (diff)
From: tomasz.figa@gmail.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] pinctrl: samsung: Allow pin value to be initialized using pinfunc
Date: Wed, 09 Jul 2014 10:07:22 +0200 [thread overview]
Message-ID: <53BCF83A.5000403@gmail.com> (raw)
In-Reply-To: <CACRpkdbZXNCHWOK0J2BCKoZN723FwosZQEa2wQHW4KpqX9EvrQ@mail.gmail.com>
On 09.07.2014 09:35, Linus Walleij wrote:
> On Wed, Jul 2, 2014 at 5:41 PM, Tomasz Figa <t.figa@samsung.com> wrote:
>
>> This patch extends the range of settings configurable via pinfunc API
>> to cover pin value as well. This allows configuration of default values
>> of pins, which is useful for pins that are not supposed to be used by
>> any dedicated driver, but need certain board-specific setting.
>>
>> Signed-off-by: Tomasz Figa <t.figa@samsung.com>
>> Acked-by: Kyungmin Park <kyungmin.park@samsung.com>
>
> Patch applied.
Thanks!
> It always makes me a little bit sad that we didn't get
> generic pin config in place before this driver but now we have to live
> with it.
That's true. :(
Best regards,
Tomasz
next prev parent reply other threads:[~2014-07-09 8:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 15:40 [PATCH 0/6] Various improvements for samsung-pinctrl driver Tomasz Figa
2014-07-02 15:40 ` Tomasz Figa
2014-07-02 15:40 ` [PATCH 1/6] pinctrl: samsung: Decouple direction setting from pinctrl Tomasz Figa
2014-07-02 15:40 ` Tomasz Figa
2014-07-08 8:54 ` Linus Walleij
2014-07-08 8:54 ` Linus Walleij
2014-07-02 15:41 ` [PATCH 2/6] pinctrl: samsung: Handle GPIO request and free using pinctrl helpers Tomasz Figa
2014-07-02 15:41 ` Tomasz Figa
2014-07-04 9:41 ` Sachin Kamat
2014-07-04 9:41 ` Sachin Kamat
2014-07-04 11:00 ` Tomasz Figa
2014-07-04 11:00 ` Tomasz Figa
2014-07-08 8:57 ` Linus Walleij
2014-07-08 8:57 ` Linus Walleij
2014-07-02 15:41 ` [PATCH 3/6] pinctrl: exynos: Consolidate irq_chips of GPIO and WKUP EINTs Tomasz Figa
2014-07-02 15:41 ` Tomasz Figa
2014-07-08 8:59 ` Linus Walleij
2014-07-08 8:59 ` Linus Walleij
2014-07-02 15:41 ` [PATCH 4/6] pinctrl: exynos: Lock GPIOs as interrupts when used as EINTs Tomasz Figa
2014-07-02 15:41 ` Tomasz Figa
2014-07-08 9:03 ` Linus Walleij
2014-07-08 9:03 ` Linus Walleij
2014-07-08 10:50 ` Tomasz Figa
2014-07-08 10:50 ` Tomasz Figa
2014-07-02 15:41 ` [PATCH 5/6] pinctrl: samsung: Allow grouping multiple pinmux/pinconf nodes Tomasz Figa
2014-07-02 15:41 ` Tomasz Figa
2014-07-09 7:32 ` Linus Walleij
2014-07-09 7:32 ` Linus Walleij
2014-07-09 8:06 ` Tomasz Figa
2014-07-09 8:06 ` Tomasz Figa
2014-07-02 15:41 ` [PATCH 6/6] pinctrl: samsung: Allow pin value to be initialized using pinfunc Tomasz Figa
2014-07-02 15:41 ` Tomasz Figa
2014-07-09 7:35 ` Linus Walleij
2014-07-09 7:35 ` Linus Walleij
2014-07-09 8:07 ` Tomasz Figa [this message]
2014-07-09 8:07 ` Tomasz Figa
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=53BCF83A.5000403@gmail.com \
--to=tomasz.figa@gmail.com \
--cc=dianders@chromium.org \
--cc=kgene.kim@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=t.figa@samsung.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 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.