mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: Kuldeep Singh <kuldeep.singh@nxp.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Mark Brown <broonie@kernel.org>
Cc: Ashish Kumar <ashish.kumar@nxp.com>,
	Rob Herring <robh+dt@kernel.org>,
	Yogesh Gaur <yogeshgaur.83@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [EXT] [PATCH v2 2/4] dt-bindings: spi: add compatible entry for imx8mp in FlexSPI controller
Date: Tue, 9 Mar 2021 07:44:18 +0100	[thread overview]
Message-ID: <0a7e8287-b5f8-99ec-d521-0a85614461e2@denx.de> (raw)
In-Reply-To: <DB6PR0402MB275899B5183869C7D471118AE0929@DB6PR0402MB2758.eurprd04.prod.outlook.com>

Hello Kuldeep,

On 09.03.21 07:29, Kuldeep Singh wrote:
>> Hi!
>>
>> On 09.03.21 06:56, Kuldeep Singh wrote:
>>> Hi Heiko,
>>>
>>>> -----Original Message-----
>>>> From: Heiko Schocher <hs@denx.de>
>>>> Sent: Tuesday, March 9, 2021 11:01 AM
>>>> To: linux-arm-kernel@lists.infradead.org
>>>> Cc: Heiko Schocher <hs@denx.de>; Ashish Kumar <ashish.kumar@nxp.com>;
>>>> Mark Brown <broonie@kernel.org>; Rob Herring <robh+dt@kernel.org>;
>>>> Yogesh Gaur <yogeshgaur.83@gmail.com>; devicetree@vger.kernel.org;
>>>> linux- kernel@vger.kernel.org; linux-spi@vger.kernel.org
>>>> Subject: [EXT] [PATCH v2 2/4] dt-bindings: spi: add compatible entry
>>>> for imx8mp in FlexSPI controller
>>>>
>>>> Caution: EXT Email
>>>>
>>>> add compatible entry "nxp,imx8mp-fspi" in NXP FlexSPI controller
>>>>
>>>> Signed-off-by: Heiko Schocher <hs@denx.de>
>>>> ---
>>>>
>>>> (no changes since v1)
>>>>
>>>>  Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
>>>> b/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
>>>> index 7ac60d9fe3571..fd5f081f6d91b 100644
>>>> --- a/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
>>>> +++ b/Documentation/devicetree/bindings/spi/spi-nxp-fspi.txt
>>>> @@ -4,6 +4,7 @@ Required properties:
>>>>    - compatible : Should be "nxp,lx2160a-fspi"
>>>>                             "nxp,imx8qxp-fspi"
>>>>                             "nxp,imx8mm-fspi"
>>>> +                           "nxp,imx8mp-fspi"
>>>
>>> It seems the changes are not on top of tree. Please see[1] for latest changes
>> including imx8dxl entry.
>>> Snippet below:
>>>
>>> Required properties:
>>>   - compatible : Should be "nxp,lx2160a-fspi"
>>>                           "nxp,imx8qxp-fspi"
>>>                           "nxp,imx8mm-fspi"
>>>                           "nxp,imx8dxl-fspi"
>>
>> My patches are based on mainline..
>> *   144c79ef33536 - (origin/master, origin/HEAD) Merge tag 'perf-tools-fixes-for-
>> v5.12-2020-03-07'
>> of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux (vor 32 Stunden)
>> <Linus Torvalds>
>>
>> Should I post this patch rebased on [1] or may all patches rebased on [1] ?
> 
> Hi Heiko,
> 
> As per cover letter, I can identify that first two are driver/Documentation patches and other two are device-tree patches.
> Device-tree patches(3/4 and 4/4) will go via Shawn tree (git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git)
> And initial two driver patches(1/4 and 2/4) will go via Mark's tree (git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git)
> 
> One approach I can think of is to send driver patches first and later send device-tree patches mentioning dependency on first two patches.

Yep, seems a good approach to me.

> Maybe Mark can comment here if he has any other opinion.

Yep, will wait for more comments, and if all is fine with this
patchset, I can split it into 2 series.

Thanks!

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: hs@denx.de

  reply	other threads:[~2021-03-09  6:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09  5:31 [PATCH v2 0/4] enable flexspi support on imx8mp Heiko Schocher
2021-03-09  5:31 ` [PATCH v2 1/4] spi: fspi: enable fspi driver for " Heiko Schocher
2021-03-09  5:31 ` [PATCH v2 2/4] dt-bindings: spi: add compatible entry for imx8mp in FlexSPI controller Heiko Schocher
2021-03-09  5:56   ` [EXT] " Kuldeep Singh
2021-03-09  6:06     ` Heiko Schocher
2021-03-09  6:29       ` Kuldeep Singh
2021-03-09  6:44         ` Heiko Schocher [this message]
2021-03-09  5:31 ` [PATCH v2 3/4] arm64: dts: imx8mp: add flexspi node Heiko Schocher
2021-05-11  1:55   ` Shawn Guo
2021-03-09  5:31 ` [PATCH v2 4/4] arm64: imx8mp: imx8mp-phycore-som enable spi nor Heiko Schocher
2021-03-09  8:19 ` [PATCH v2 0/4] enable flexspi support on imx8mp Marco Felsch
2021-03-09  8:41   ` Heiko Schocher
2021-03-15  6:47 ` Shawn Guo
2021-03-15  7:10   ` Heiko Schocher
2021-03-15  7:17     ` Shawn Guo

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=0a7e8287-b5f8-99ec-d521-0a85614461e2@denx.de \
    --to=hs@denx.de \
    --cc=ashish.kumar@nxp.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kuldeep.singh@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=yogeshgaur.83@gmail.com \
    /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

all inboxes | Powered by JetHome®