From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Petr Kulhavy <petr@barix.com>,
nsekhar@ti.com, khilman@kernel.org, lgirdwood@gmail.com,
broonie@kernel.org, devicetree@vger.kernel.org
Cc: mark.rutland@arm.com, alsa-devel@alsa-project.org,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
robh+dt@kernel.org, galak@codeaurora.org
Subject: Re: [PATCH 6/6] ARM: DTS: da850: Add McBSP0 and McBSP1
Date: Thu, 7 Apr 2016 16:04:47 +0300 [thread overview]
Message-ID: <57065AEF.9080002@ti.com> (raw)
In-Reply-To: <570658BF.9010802@barix.com>
On 04/07/16 15:55, Petr Kulhavy wrote:
>
>
> On 07.04.2016 14:45, Peter Ujfalusi wrote:
>> On 04/07/16 15:16, Petr Kulhavy wrote:
>>> On 07.04.2016 13:34, Peter Ujfalusi wrote:
>>>> On 04/06/16 16:21, Petr Kulhavy wrote:
>>>>> Add SoC nodes for McBSP0 and McBSP1 as well as the corresponding pinmux
>>>>> configurations.
>>>>>
>>>>> Signed-off-by: Petr Kulhavy <petr@barix.com>
>>>>> ---
>>>>> arch/arm/boot/dts/da850.dtsi | 45
>>>>> +++++++++++++++++++++++++++++++++++++++++++-
>>>>> 1 file changed, 44 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/arch/arm/boot/dts/da850.dtsi b/arch/arm/boot/dts/da850.dtsi
>>>>> index 5996e765e59c..9e2b1e97377c 100644
>>>>> --- a/arch/arm/boot/dts/da850.dtsi
>>>>> +++ b/arch/arm/boot/dts/da850.dtsi
>>>>> @@ -148,7 +148,24 @@
>>>>> 0xc 0x88888888 0xffffffff
>>>>> >;
>>>>> };
>>>>> -
>>>>> + mcbsp0_pins: pinmux_mcbsp0_pins {
>>>>> + pinctrl-single,bits = <
>>>>> + /* PINMUX2:
>>>>> + * CLKS0, DX0, DR0, FSX0
>>>>> + * FSR0, CLKX0, CLKR0
>>>>> + */
>>>>> + 0x8 0x02222220 0xfffffff0
>>>>> + >;
>>>>> + };
>>>>> + mcbsp1_pins: pinmux_mcbsp1_pins {
>>>>> + pinctrl-single,bits = <
>>>>> + /* PINMUX1:
>>>>> + * CLKS1, DX1, DR1, FSX1,
>>>>> + * FSR1, CLKX1, CLKR1
>>>>> + */
>>>>> + 0x4 0x22222220 0xfffffff0
>>>> This will conflict with the mcasp0_pins in da850-evm as AXR11 and AXR12 is
>>>> used by the board for audio. When I say conflict, I mean that audio will be
>>>> completely broken on the board.
>>> I agree with you, the EVM uses the pins for other peripherals. However I
>>> understand that the da850.dtsi is a generic description of the DA850 platform.
>>> Other DA850 based designs that use the McBSP will not have conflicts. For
>>> instance my two AM1808 based boards don't use the McASP.
>>> Of course the board's DTS must enable only non-conflicting peripherals/pinmux
>>> configurations.
>>> But having the pinmuxes defined does not break anything and actually helps
>>> creating the DTS file.
>> I think what the da850.dtsi does is wrong. The dtsi file should not set any
>> pinmux, those need to be set by the board .dts files If one board uses McASP0,
>> it will set up the pins for that and leave McBSP pins as they were, but other
>> board might use McBSP1 and not use McASP0, there you will have pincontrol for
>> McBSP1.
> It does not set the pinmux, it just defines the configurations.
> As far as I understand the pin configuration is applied when a node includes
> these two lines:
>
> pinctrl-names = "default";
> pinctrl-0 = <&mcbspc0_pins>;
Yeah, true. just ignore my comment for the pinctrl part...
>
> Petr
>
--
Péter
next prev parent reply other threads:[~2016-04-07 13:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 13:21 [PATCH 0/6] ASoC: davinci-mcbsp: add binding for McBSP Petr Kulhavy
[not found] ` <1459948893-4206-1-git-send-email-petr-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-06 13:21 ` [PATCH 1/6] " Petr Kulhavy
2016-04-07 13:33 ` Peter Ujfalusi
[not found] ` <570661A6.6020804-l0cyMroinI0@public.gmane.org>
2016-04-07 15:37 ` [alsa-devel] " Petr Kulhavy
2016-04-08 9:24 ` Petr Kulhavy
2016-04-11 8:11 ` Peter Ujfalusi
[not found] ` <570B5C26.9080402-l0cyMroinI0@public.gmane.org>
2016-04-11 8:20 ` [alsa-devel] " Petr Kulhavy
2016-04-06 13:21 ` [PATCH 2/6] ASoC: Davinci: McBSP: add device tree support " Petr Kulhavy
2016-04-07 12:42 ` Peter Ujfalusi
[not found] ` <570655BE.7030109-l0cyMroinI0@public.gmane.org>
2016-04-07 13:32 ` [alsa-devel] " Petr Kulhavy
2016-04-07 13:45 ` Peter Ujfalusi
2016-04-06 13:21 ` [PATCH 3/6] ARM: davinci: da850: add clocks for mcbsp0 and 1 Petr Kulhavy
2016-04-06 13:21 ` [PATCH 4/6] ARM: davinci: da8xx-dt: add OF_DEV_AUXDATA entries for mcbsp0 and mcbsp1 Petr Kulhavy
2016-04-06 13:21 ` [PATCH 5/6] ARM: DTS: da850: Fix wrong number of interrupts Petr Kulhavy
2016-04-06 13:21 ` [PATCH 6/6] ARM: DTS: da850: Add McBSP0 and McBSP1 Petr Kulhavy
2016-04-07 11:34 ` Peter Ujfalusi
[not found] ` <570645B4.6060606-l0cyMroinI0@public.gmane.org>
2016-04-07 12:16 ` [alsa-devel] " Petr Kulhavy
[not found] ` <57064F8B.3020501-Qh/3xLP0EvwAvxtiuMwx3w@public.gmane.org>
2016-04-07 12:45 ` Peter Ujfalusi
[not found] ` <5706567B.5000501-l0cyMroinI0@public.gmane.org>
2016-04-07 12:55 ` Petr Kulhavy
2016-04-07 13:04 ` Peter Ujfalusi [this message]
2016-04-07 13:05 ` Sekhar Nori
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=57065AEF.9080002@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=khilman@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--cc=pawel.moll@arm.com \
--cc=petr@barix.com \
--cc=robh+dt@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).