From mboxrd@z Thu Jan 1 00:00:00 1970 From: jiri.prchal@aksignal.cz (=?UTF-8?B?SmnFmcOtIFByY2hhbA==?=) Date: Fri, 25 Jul 2014 12:06:30 +0200 Subject: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO In-Reply-To: <20140725113110.70c4aa41@bbrezillon> References: <1405074175-22444-1-git-send-email-voice.shen@atmel.com> <53D10C50.50305@aksignal.cz> <20140724162645.4e19c26c@bbrezillon> <53D12103.3020103@aksignal.cz> <20140724175848.44f5da10@bbrezillon> <53D1F5D0.1080006@aksignal.cz> <20140725095319.16a8465c@bbrezillon> <53D214E1.4050105@aksignal.cz> <20140725104553.403921b1@bbrezillon> <53D21B3F.7060006@aksignal.cz> <20140725110124.3f0dce6c@bbrezillon> <53D21FCF.7010402@aksignal.cz> <20140725113110.70c4aa41@bbrezillon> Message-ID: <53D22C26.4030208@aksignal.cz> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Dne 25.7.2014 v 11:31 Boris BREZILLON napsal(a): > On Fri, 25 Jul 2014 11:13:51 +0200 > Ji?? Prchal wrote: > > >>> >>> Every thing seems in place. >>> Could you enable CONFIG_DEBUG_PINCTRL and grep on "enable pin" ? >> / # dmesg | grep "enable pin" >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 101 as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 101 as PIOD5 0x20 >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 100 as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 100 as PIOD4 0x10 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 23 as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 23 as PIOA23 0x800000 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 22 as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 22 as PIOA22 0x400000 >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 93 as GPIO >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 93 as PIOC29 0x20000000 >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 14 as GPIO >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl at fffff400: enable pin 14 as PIOA14 0x4000 > > > Okay, this cleary shows that PA14 pin is muxed as a GPIO (or at least > the driver think it is). > > > Could you launch these commands (you'll need the devmem tool) and > paste the results ? > > #devmem 0xfffff408 > #devmem 0xfffff418 > #devmem 0xfffff438 > #devmem 0xfffff43c > #devmem 0xfffff458 > #devmem 0xfffff468 > #devmem 0xfffff470 > #devmem 0xfffff474 > #devmem 0xfffff498 > / # devmem 0xfffff408 0xF0E04018 / # devmem 0xfffff418 0xE0C04000 / # devmem 0xfffff438 0x00C04000 / # devmem 0xfffff43c 0x13FFD7FB / # devmem 0xfffff458 0x00000000 / # devmem 0xfffff468 0xFF223B4E / # devmem 0xfffff470 0x0F000000 / # devmem 0xfffff474 0x00000000 / # devmem 0xfffff498 0xFFFFFFFF I get thought if is possible that in time of probe fm25 (it's first) is not configured PA14 (it 's last)? From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?SmnFmcOtIFByY2hhbA==?= Subject: Re: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO Date: Fri, 25 Jul 2014 12:06:30 +0200 Message-ID: <53D22C26.4030208@aksignal.cz> References: <1405074175-22444-1-git-send-email-voice.shen@atmel.com> <53D10C50.50305@aksignal.cz> <20140724162645.4e19c26c@bbrezillon> <53D12103.3020103@aksignal.cz> <20140724175848.44f5da10@bbrezillon> <53D1F5D0.1080006@aksignal.cz> <20140725095319.16a8465c@bbrezillon> <53D214E1.4050105@aksignal.cz> <20140725104553.403921b1@bbrezillon> <53D21B3F.7060006@aksignal.cz> <20140725110124.3f0dce6c@bbrezillon> <53D21FCF.7010402@aksignal.cz> <20140725113110.70c4aa41@bbrezillon> Reply-To: jiri.prchal-cKCO0sOKHLPtwjQa/ONI9g@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: <20140725113110.70c4aa41@bbrezillon> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Boris BREZILLON Cc: Bo Shen , nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: devicetree@vger.kernel.org Dne 25.7.2014 v 11:31 Boris BREZILLON napsal(a): > On Fri, 25 Jul 2014 11:13:51 +0200 > Ji=C5=99=C3=AD Prchal wrote: > > >>> >>> Every thing seems in place. >>> Could you enable CONFIG_DEBUG_PINCTRL and grep on "enable pin" ? >> / # dmesg | grep "enable pin" >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 101= as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 101= as PIOD5 0x20 >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 100= as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 100= as PIOD4 0x10 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 23 = as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 23 = as PIOA23 0x800000 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 22 = as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 22 = as PIOA22 0x400000 >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 93 = as GPIO >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 93 = as PIOC29 0x20000000 >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 14 = as GPIO >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 14 = as PIOA14 0x4000 > > > Okay, this cleary shows that PA14 pin is muxed as a GPIO (or at least > the driver think it is). > > > Could you launch these commands (you'll need the devmem tool) and > paste the results ? > > #devmem 0xfffff408 > #devmem 0xfffff418 > #devmem 0xfffff438 > #devmem 0xfffff43c > #devmem 0xfffff458 > #devmem 0xfffff468 > #devmem 0xfffff470 > #devmem 0xfffff474 > #devmem 0xfffff498 > / # devmem 0xfffff408 0xF0E04018 / # devmem 0xfffff418 0xE0C04000 / # devmem 0xfffff438 0x00C04000 / # devmem 0xfffff43c 0x13FFD7FB / # devmem 0xfffff458 0x00000000 / # devmem 0xfffff468 0xFF223B4E / # devmem 0xfffff470 0x0F000000 / # devmem 0xfffff474 0x00000000 / # devmem 0xfffff498 0xFFFFFFFF I get thought if is possible that in time of probe fm25 (it's first) is= not configured PA14 (it 's last)? -- To unsubscribe from this list: send the line "unsubscribe devicetree" i= n the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759980AbaGYKG5 (ORCPT ); Fri, 25 Jul 2014 06:06:57 -0400 Received: from [188.175.113.102] ([188.175.113.102]:57542 "EHLO router.aksignal.cz" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1751113AbaGYKGz (ORCPT ); Fri, 25 Jul 2014 06:06:55 -0400 Message-ID: <53D22C26.4030208@aksignal.cz> Date: Fri, 25 Jul 2014 12:06:30 +0200 From: =?UTF-8?B?SmnFmcOtIFByY2hhbA==?= Reply-To: jiri.prchal@aksignal.cz Organization: AK signal Brno User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Boris BREZILLON CC: Bo Shen , nicolas.ferre@atmel.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH] ARM: at91: at91sam9x5: sets NPCS0 (PA14) back to GPIO References: <1405074175-22444-1-git-send-email-voice.shen@atmel.com> <53D10C50.50305@aksignal.cz> <20140724162645.4e19c26c@bbrezillon> <53D12103.3020103@aksignal.cz> <20140724175848.44f5da10@bbrezillon> <53D1F5D0.1080006@aksignal.cz> <20140725095319.16a8465c@bbrezillon> <53D214E1.4050105@aksignal.cz> <20140725104553.403921b1@bbrezillon> <53D21B3F.7060006@aksignal.cz> <20140725110124.3f0dce6c@bbrezillon> <53D21FCF.7010402@aksignal.cz> <20140725113110.70c4aa41@bbrezillon> In-Reply-To: <20140725113110.70c4aa41@bbrezillon> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dne 25.7.2014 v 11:31 Boris BREZILLON napsal(a): > On Fri, 25 Jul 2014 11:13:51 +0200 > Jiří Prchal wrote: > > >>> >>> Every thing seems in place. >>> Could you enable CONFIG_DEBUG_PINCTRL and grep on "enable pin" ? >> / # dmesg | grep "enable pin" >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 101 as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 101 as PIOD5 0x20 >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 100 as GPIO >> [ 0.968750] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 100 as PIOD4 0x10 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 23 as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 23 as PIOA23 0x800000 >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 22 as GPIO >> [ 1.238281] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 22 as PIOA22 0x400000 >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 93 as GPIO >> [ 1.242187] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 93 as PIOC29 0x20000000 >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 14 as GPIO >> [ 1.246093] pinctrl-at91 ahb:apb:pinctrl@fffff400: enable pin 14 as PIOA14 0x4000 > > > Okay, this cleary shows that PA14 pin is muxed as a GPIO (or at least > the driver think it is). > > > Could you launch these commands (you'll need the devmem tool) and > paste the results ? > > #devmem 0xfffff408 > #devmem 0xfffff418 > #devmem 0xfffff438 > #devmem 0xfffff43c > #devmem 0xfffff458 > #devmem 0xfffff468 > #devmem 0xfffff470 > #devmem 0xfffff474 > #devmem 0xfffff498 > / # devmem 0xfffff408 0xF0E04018 / # devmem 0xfffff418 0xE0C04000 / # devmem 0xfffff438 0x00C04000 / # devmem 0xfffff43c 0x13FFD7FB / # devmem 0xfffff458 0x00000000 / # devmem 0xfffff468 0xFF223B4E / # devmem 0xfffff470 0x0F000000 / # devmem 0xfffff474 0x00000000 / # devmem 0xfffff498 0xFFFFFFFF I get thought if is possible that in time of probe fm25 (it's first) is not configured PA14 (it 's last)?