From: Arend van Spriel <arend@broadcom.com>
To: "Jörg Krause" <jk@lintech.de>,
linux-kernel@vger.kernel.org,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>
Subject: Re: [RFC] dt: bindings: add bindings for Broadcom bcm43xx sdio devices
Date: Fri, 11 Apr 2014 10:06:52 +0200 [thread overview]
Message-ID: <5347A29C.7020602@broadcom.com> (raw)
In-Reply-To: <1397165245229-838046.post@n7.nabble.com>
On 10/04/14 23:27, Jörg Krause wrote:
> On 02/13/14 10:28, Chen-Yu Tsai wrote:
>> Hi,
>>
>> On Thu, Feb 13, 2014 at 5:13 PM, Tomasz Figa<tomasz.figa@> wrote:
>>> Hi Arend,
>>>
>>>
>>> On 10.02.2014 20:17, Arend van Spriel wrote:
>
> [...]
>
> Hi Chen-Yu,
>
> picking up this thread.
>
>> AFAIK, the pinctrl in tied to the device node, and is selected when the
>> device
>> is registered. The MMC subsystem currently does not register child nodes,
>> so
>> this would be useless.
>
> So if MMC does not register child nodes, brcmfmac will not be probed
> with of_node set? Have there been patches submitted for this in mmc
> subsystem recently.
>
> [...]
>
>
>
> Sascha Hauer submitted a patch a week ago. Link:
> https://lkml.org/lkml/2014/4/3/522 <https://lkml.org/lkml/2014/4/3/522>
Thanks, Jörg
It is a partial solution, but it seems to conflict with my change. So
thanks for the heads up. I am not convinced whether the GPIO and clock
should be bound to the function. They seem more a property of the
card/device inserted.
Regards,
Arend
> --
> View this message in context: http://linux-kernel.2935.n7.nabble.com/RFC-dt-bindings-add-bindings-for-Broadcom-bcm43xx-sdio-devices-tp801976p838046.html
> Sent from the Linux Kernel mailing list archive at Nabble.com.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-04-11 8:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 19:17 [RFC] dt: bindings: add bindings for Broadcom bcm43xx sdio devices Arend van Spriel
2014-02-10 19:17 ` Arend van Spriel
2014-02-13 7:41 ` Chen-Yu Tsai
[not found] ` <1392059868-8782-1-git-send-email-arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2014-02-13 9:13 ` Tomasz Figa
2014-02-13 9:13 ` Tomasz Figa
[not found] ` <52FC8CB3.4090305-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-02-13 9:28 ` Chen-Yu Tsai
2014-02-13 9:28 ` Chen-Yu Tsai
2014-03-30 8:56 ` Arend van Spriel
2014-04-10 21:27 ` Jörg Krause
2014-04-11 8:06 ` Arend van Spriel [this message]
2014-02-13 12:07 ` Arend van Spriel
2014-02-13 12:07 ` Arend van Spriel
2014-02-13 12:35 ` Tomasz Figa
2014-02-13 16:22 ` Mark Brown
2014-03-31 8:24 ` Ulf Hansson
2014-03-31 16:10 ` Mark Brown
2014-03-31 16:10 ` Mark Brown
2014-02-25 22:51 ` Stephen Warren
2014-03-13 10:16 ` Arend van Spriel
2014-03-13 10:16 ` Arend van Spriel
2014-03-13 10:42 ` Tomasz Figa
[not found] ` <53218B9F.7030904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-13 13:00 ` Arend van Spriel
2014-03-13 13:00 ` Arend van Spriel
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=5347A29C.7020602@broadcom.com \
--to=arend@broadcom.com \
--cc=jk@lintech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=s.hauer@pengutronix.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.