public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>
Cc: paul@crapouillou.net, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	dongsheng.qiu@ingenic.com, aric.pzqi@ingenic.com,
	rick.tyliu@ingenic.com
Subject: Re: [PATCH 0/3] Refresh device tree and defconfig for Ingenic SoCs and boards.
Date: Mon, 23 May 2022 11:19:17 +0200	[thread overview]
Message-ID: <20220523091916.GF5069@alpha.franken.de> (raw)
In-Reply-To: <1652384021-46309-1-git-send-email-zhouyanjie@wanyeetech.com>

On Fri, May 13, 2022 at 03:33:38AM +0800, 周琰杰 (Zhou Yanjie) wrote:
> 1.Add PWM node for X1830 SoC from Ingenic.
> 2.Add SSI nodes for X1000 SoC and X1830 SoC from Ingenic.
> 3.Refresh SSI related nodes in CU1000-Neo and CU1830-Neo.
> 4.The X1830 SoC used by the CU1830-Neo and the X1000 SoC
>   used by the CU1000-Neo are both single-core processors,
>   therefore the "OST_CLK_PERCPU_TIMER" ABI should not be
>   used in the OST nodes of the CU1830-Neo and CU1000-Neo,
>   it is just a coincidence that there is no problem now.
>   So replace the misused "OST_CLK_PERCPU_TIMER" ABI with
>   the correct "OST_CLK_EVENT_TIMER" ABI.
> 5.Refresh the defconfig files of the CU1000-Neo board and
>   the CU1830-Neo board, remove the selection of SPI-GPIO,
>   and add the selection of SSI.
> 
> 周琰杰 (Zhou Yanjie) (3):
>   MIPS: Ingenic: Add PWM nodes for X1830.
>   MIPS: Ingenic: Refresh device tree for Ingenic SoCs and boards.
>   MIPS: Ingenic: Refresh defconfig for CU1000-Neo and CU1830-Neo.
> 
>  arch/mips/boot/dts/ingenic/cu1000-neo.dts | 77 ++++++++++++++++---------------
>  arch/mips/boot/dts/ingenic/cu1830-neo.dts | 76 +++++++++++++++---------------
>  arch/mips/boot/dts/ingenic/x1000.dtsi     | 20 ++++++++
>  arch/mips/boot/dts/ingenic/x1830.dtsi     | 53 +++++++++++++++++++++
>  arch/mips/configs/cu1000-neo_defconfig    |  2 +-
>  arch/mips/configs/cu1830-neo_defconfig    |  2 +-
>  6 files changed, 154 insertions(+), 76 deletions(-)
> 
> -- 
> 2.7.4

seried applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2022-05-23  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-12 19:33 [PATCH 0/3] Refresh device tree and defconfig for Ingenic SoCs and boards 周琰杰 (Zhou Yanjie)
2022-05-12 19:33 ` [PATCH 1/3] MIPS: Ingenic: Add PWM nodes for X1830 周琰杰 (Zhou Yanjie)
2022-05-12 19:33 ` [PATCH 2/3] MIPS: Ingenic: Refresh device tree for Ingenic SoCs and boards 周琰杰 (Zhou Yanjie)
2022-05-12 19:33 ` [PATCH 3/3] MIPS: Ingenic: Refresh defconfig for CU1000-Neo and CU1830-Neo 周琰杰 (Zhou Yanjie)
2022-05-23  9:19 ` Thomas Bogendoerfer [this message]

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=20220523091916.GF5069@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=aric.pzqi@ingenic.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dongsheng.qiu@ingenic.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paul@crapouillou.net \
    --cc=rick.tyliu@ingenic.com \
    --cc=robh+dt@kernel.org \
    --cc=zhouyanjie@wanyeetech.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