linux-kernel - Re: [GIT PULL 1/4] bcm2835 arm DT updates for 4.12

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1533334801.217079.1490439824805@email.1und1.de>
Date:   Sat, 25 Mar 2017 12:03:44 +0100 (CET)
From:   Stefan Wahren <stefan.wahren@...e.com>
To:     Eric Anholt <eric@...olt.net>, Arnd Bergmann <arnd@...db.de>
Cc:     Lee Jones <lee@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        bcm-kernel-feedback-list@...adcom.com,
        Stephen Warren <swarren@...dotorg.org>,
        Florian Fainelli <f.fainelli@...il.com>,
        linux-rpi-kernel@...ts.infradead.org,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [GIT PULL 1/4] bcm2835 arm DT updates for 4.12

Hi Arnd,

i hope it's okay if i answer.

> Arnd Bergmann <arnd@...db.de> hat am 24. März 2017 um 23:25 geschrieben:
> 
> 
> On Tue, Mar 21, 2017 at 8:39 PM, Eric Anholt <eric@...olt.net> wrote:
> >   Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
> >
> > are available in the git repository at:
> >
> >   git://github.com/anholt/linux tags/bcm2835-dt-next-2017-03-21
> >
> > for you to fetch changes up to 7f31a955a0c34de0463f7ff50b2bd62a5cce4204:
> >
> >   ARM: dts: bcm2835: add sdhost controller to devicetree (2017-03-17 17:35:50 -0700)
> >
> > ----------------------------------------------------------------
> > This pull request brings in the DT nodes for enabling HDMI audio on
> > Raspberry Pi, and nodes to describe the DSI and SDHOST hardware
> > modules (which are still disabled by default).
> 
> Just a quick question: how do you plan to switch between the SD host
> drivers? If I understand this right, there are two working hardware blocks
> that can connect to the same slot. Do you have to configure this in
> device tree using  hardwired pinctrl settings, or can the user pick
> one of the drivers at runtime?

via device tree

The relevant changes [1] hasn't been merged yet.

[1] - http://marc.info/?l=linux-mmc&m=148896494931931&w=2

> 
>         Arnd