All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Codrin.Ciubotariu@microchip.com>
To: <Eugen.Hristev@microchip.com>, <robh+dt@kernel.org>,
	<Nicolas.Ferre@microchip.com>
Cc: <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <soc@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <Claudiu.Beznea@microchip.com>
Subject: Re: [PATCH 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek
Date: Tue, 11 May 2021 15:17:39 +0000	[thread overview]
Message-ID: <69db39fe-e969-f637-7226-5cb63fc477c5@microchip.com> (raw)
In-Reply-To: <20210507152655.182558-2-eugen.hristev@microchip.com>


> +#define PIN_PC16			80
> +#define PIN_PC16__GPIO			PINMUX_PIN(PIN_PC16, 0, 0)
> +#define PIN_PC16__I2SMCC_DOUT2		PINMUX_PIN(PIN_PC16, 1, 1)

This one should be PIN_PC16__I2SMCC1_DOUT2

Best regards,
Codrin

WARNING: multiple messages have this Message-ID (diff)
From: <Codrin.Ciubotariu@microchip.com>
To: <Eugen.Hristev@microchip.com>, <robh+dt@kernel.org>,
	<Nicolas.Ferre@microchip.com>
Cc: <alexandre.belloni@bootlin.com>,
	<Ludovic.Desroches@microchip.com>, <soc@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <Claudiu.Beznea@microchip.com>
Subject: Re: [PATCH 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek
Date: Tue, 11 May 2021 15:17:39 +0000	[thread overview]
Message-ID: <69db39fe-e969-f637-7226-5cb63fc477c5@microchip.com> (raw)
Message-ID: <20210511151739.d85Gr9_hi5uUpJ-ZYcD36P5HN2yihnTpvb26SceLTqc@z> (raw)
In-Reply-To: <20210507152655.182558-2-eugen.hristev@microchip.com>


> +#define PIN_PC16			80
> +#define PIN_PC16__GPIO			PINMUX_PIN(PIN_PC16, 0, 0)
> +#define PIN_PC16__I2SMCC_DOUT2		PINMUX_PIN(PIN_PC16, 1, 1)

This one should be PIN_PC16__I2SMCC1_DOUT2

Best regards,
Codrin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-05-11 15:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-07 15:26 [PATCH 1/4] dt-bindings: ARM: at91: document sama7g5ek board Eugen Hristev
2021-05-07 15:26 ` Eugen Hristev
2021-05-07 15:26 ` [PATCH 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek Eugen Hristev
2021-05-07 15:26   ` Eugen Hristev
2021-05-10 16:00   ` Rob Herring
2021-05-10 16:00     ` Rob Herring
2021-05-11 15:17   ` Codrin.Ciubotariu [this message]
2021-05-11 15:17     ` Codrin.Ciubotariu
2021-05-07 15:26 ` [PATCH 3/4] ARM: configs: at91: add defconfig for sama7 family of SoCs Eugen Hristev
2021-05-07 15:26   ` Eugen Hristev
2021-05-07 15:26 ` [PATCH 4/4] ARM: multi_v7_defconfig: add sama7g5 SoC Eugen Hristev
2021-05-07 15:26   ` Eugen Hristev
2021-05-10 15:49 ` [PATCH 1/4] dt-bindings: ARM: at91: document sama7g5ek board Rob Herring
2021-05-10 15:49   ` Rob Herring

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=69db39fe-e969-f637-7226-5cb63fc477c5@microchip.com \
    --to=codrin.ciubotariu@microchip.com \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Eugen.Hristev@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=soc@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 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.