linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Tudor Ambarus - M18064 <Tudor.Ambarus@microchip.com>
Cc: "alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
	"Ludovic Desroches - M43218" <Ludovic.Desroches@microchip.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: at91: sama7g5: Add NAND support
Date: Fri, 25 Feb 2022 11:28:45 +0100	[thread overview]
Message-ID: <3cc35822-cbfb-28e5-5fdb-76ceb1eebd27@microchip.com> (raw)
In-Reply-To: <647e801b-88d3-6169-0354-ba1cdff8d807@microchip.com>

On 24/02/2022 at 19:26, Tudor Ambarus - M18064 wrote:
> On 2/24/22 19:44, Nicolas Ferre wrote:
>> Hi Tudor,
> 
> Hi,
> 
>>
>> On 24/02/2022 at 16:49, Tudor Ambarus - M18064 wrote:
>>> On 2/24/22 17:04, Nicolas Ferre wrote:
>>>> On 11/01/2022 at 14:05, Tudor Ambarus wrote:
>>>>> Add NAND support. The sama7g5's SMC IP is the same as sama5d2's with
>>>>> a slightly change: it provides a synchronous clock output (SMC clock)
>>>>> that is dedicated to FPGA usage. Since this doesn't interfere with the SMC
>>>>> NAND configuration, thus code will not be added in the current nand driver
>>>>> to address the FPGA usage, use the sama5d2's compatible and choose not to
>>>>> introduce dedicated compatibles for sama7g5.
>>>>> Tested with Micron MT29F4G08ABAEAWP NAND flash.
>>>>>
>>>>> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
>>>>
>>>> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>>>>
>>>>> ---
>>>>> The patch depends on the following patch:
>>>>> https://lore.kernel.org/linux-clk/20220111125310.902856-1-tudor.ambarus@microchip.com/T/#u
>>>>
>>>> Patch seems taken, so I add this one to at91-dt branch for 5.18 merge window.
>>>>
>>>
>>> I think it depends on who gets to next first. If at91 gets before clk,
>>> there will be a build error, isn't it?
>>
> 
> Sorry, not linux-next, but whose PR gets first applied by Linus.
> 
>> Clk patch is already in linux-next, so no worries.
>> Moreover, I don't get why there could be a build error as there is no build dependency between DT changes and C changes.
>> Sorry but I'm puzzled... Or I'm not looking at the right patch.
>>
> 
> You would see this kind of error:
> Error: arch/arm/boot/dts/sama7g5.dtsi:102.21-22 syntax error
> FATAL ERROR: Unable to parse input tree
> make[1]: *** [scripts/Makefile.lib:346: arch/arm/boot/dts/at91-sama7g5ek.dtb] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make: *** [Makefile:1385: dtbs] Error 2
> make: *** Waiting for unfinished jobs....
> 
> This patch uses "PMC_MCK1" which is defined in:
> https://lore.kernel.org/linux-clk/20220111125310.902856-1-tudor.ambarus@microchip.com/T/#u
> 
> If Linus applies the arm-soc PR before the clk PR, it will see the same error, no?

Yes, absolutely.
So I need to have an immutable branch from Stephen then. I'm removing 
the patch from the at91-dt branch for now.

Thanks for the insight and sorry not having overlooked at that crucial 
piece of header file ;-)

Best regards,
   Nicolas

-- 
Nicolas Ferre

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

  reply	other threads:[~2022-02-25 10:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 13:05 [PATCH] ARM: dts: at91: sama7g5: Add NAND support Tudor Ambarus
2022-02-24 15:04 ` Nicolas Ferre
2022-02-24 15:49   ` Tudor.Ambarus
2022-02-24 17:44     ` Nicolas Ferre
2022-02-24 18:26       ` Tudor.Ambarus
2022-02-25 10:28         ` Nicolas Ferre [this message]
2022-03-04 14:12           ` Nicolas Ferre

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=3cc35822-cbfb-28e5-5fdb-76ceb1eebd27@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Tudor.Ambarus@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 \
    /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).