All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pinctrl: renesas: Fix linker error when PINCTRL_PFC=n
Date: Thu, 4 Apr 2019 14:42:36 +0200	[thread overview]
Message-ID: <20190404124236.GA29742@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <f2e17121-674f-d24f-dd61-f3fd60728cbb@gmail.com>

Hi Marek,

On Thu, Apr 04, 2019 at 03:36:45AM +0200, Marek Vasut wrote:
[..]
> I was thinking about this patch further and I think the best way forward
> would be to extend the pinmux/pinctrl API with a callback to set a pin
> as GPIO and then just call that API from the GPIO driver. That would be
> the generic solution and would make this whole
> sh_pfc_config_mux_for_gpio() go away altogether.

I don't think anybody is going to contradict you, as long as your
solution resolves/prevents the build error reported in this thread.

Since you have the best vision of it, I assume you take the ownership
of the change and CC the relevant people upon patch submission?

Best regards,
Eugeniu.

  reply	other threads:[~2019-04-04 12:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 13:18 [U-Boot] [PATCH] pinctrl: renesas: Fix linker error when PINCTRL_PFC=n Eugeniu Rosca
2019-04-02 13:34 ` Marek Vasut
2019-04-02 15:17   ` Dirk Behme
2019-04-02 15:28     ` Marek Vasut
2019-04-02 15:40       ` Eugeniu Rosca
2019-04-02 16:02         ` Marek Vasut
2019-04-02 17:02           ` Eugeniu Rosca
2019-04-03 12:11             ` Marek Vasut
2019-04-03 12:30               ` Dirk Behme
2019-04-03 14:01                 ` Marek Vasut
2019-04-04  1:36                   ` Marek Vasut
2019-04-04 12:42                     ` Eugeniu Rosca [this message]
2019-04-21 22:23                       ` Marek Vasut
2019-04-02 17:58         ` Dirk Behme
2019-04-03 12:08           ` Marek Vasut

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=20190404124236.GA29742@vmlxhi-102.adit-jv.com \
    --to=erosca@de.adit-jv.com \
    --cc=u-boot@lists.denx.de \
    /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.