From: James Hogan <jhogan@kernel.org>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Ralf Baechle <ralf@linux-mips.org>,
Michael Turquette <mturquette@baylibre.com>,
sboyd@codeaurora.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-MIPS <linux-mips@linux-mips.org>,
linux-clk@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
Paul Cercueil <paul@crapouillou.net>,
Mathieu Malaterre <malat@debian.org>,
Dominik Peklo <dom.peklo@gmail.com>
Subject: Re: [RFC 3/4] MIPS: Ingenic: Initial X1000 SoC support
Date: Wed, 7 Mar 2018 15:10:25 +0000 [thread overview]
Message-ID: <20180307151025.GP4197@saruman> (raw)
In-Reply-To: <CANc+2y5wsvGWszu3pePYhs2wb1_AgPdjG+ugfOCzbZVfVHDMvw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
On Wed, Mar 07, 2018 at 08:35:00PM +0530, PrasannaKumar Muralidharan wrote:
> On 7 March 2018 at 20:05, James Hogan <jhogan@kernel.org> wrote:
> > On Wed, Mar 07, 2018 at 07:14:49PM +0530, PrasannaKumar Muralidharan wrote:
> >> > Does X1000 use a different PRID, or is it basically just a JZ4780 core
> >> > with different SoC peripherals?
> >>
> >> Yes X1000 does have a different PRID (PRID = 0x2ed1024f). X1000 has
> >
> > Right, so thats 0x2e000000 | PRID_COMP_INGENIC_D1 | PRID_IMP_JZRISC |
> > 0x4f, which cpu-probe.c already handles (apparently the D1 company code
> > is used for JZ4770 & JZ4775 too).
>
> Okay. Does this mean I need not modify get_board_mach_type() and
> get_system_type()?
You still need to modify them, otherwise it won't understand
"ingenic,x1000" compatible string, and will call it a JZ4740 in
/proc/cpuinfo.
> >> I used to get my code tested from Domink but I could not reach him for
> >> quite some time. Before buying the development board myself I would
> >> like to see if anyone can help me in testing. Do you have any contact
> >> with Ingenic who can help in testing this?
> >
> > Not personally, but I'll ask around. Of course if nobody much cares
> > about it in practice and nobody has the hardware, there may be little
> > value in supporting it upstream.
>
> Seems Jiaxun is interested in the board and is willing to help.
Okay, cool.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-07 15:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 15:15 [RFC 0/4] Add Ingenic X1000 SoC Support PrasannaKumar Muralidharan
2017-09-27 15:15 ` [RFC 1/4] dt-bindings: Add Ingenic X1000 SoC clock define PrasannaKumar Muralidharan
2017-09-27 15:15 ` [RFC 2/4] clk: Add Ingenic X1000 CGU driver PrasannaKumar Muralidharan
2017-10-25 9:23 ` Stephen Boyd
2017-09-27 15:15 ` [RFC 3/4] MIPS: Ingenic: Initial X1000 SoC support PrasannaKumar Muralidharan
2018-03-06 0:08 ` James Hogan
2018-03-07 13:44 ` PrasannaKumar Muralidharan
2018-03-07 14:19 ` Jiaxun Yang
2018-03-07 15:21 ` PrasannaKumar Muralidharan
2018-03-07 15:21 ` PrasannaKumar Muralidharan
2018-03-07 14:35 ` James Hogan
2018-03-07 15:05 ` PrasannaKumar Muralidharan
2018-03-07 15:10 ` James Hogan [this message]
2018-03-07 15:22 ` PrasannaKumar Muralidharan
2018-03-07 15:52 ` Jiaxun Yang
2018-03-07 16:25 ` PrasannaKumar Muralidharan
2018-03-07 16:25 ` PrasannaKumar Muralidharan
2018-03-07 18:13 ` Mathieu Malaterre
2018-03-07 18:13 ` Mathieu Malaterre
2018-03-10 19:05 ` Jiaxun Yang
2018-03-09 0:52 ` Jiaxun Yang
2017-09-27 15:15 ` [RFC 4/4] MIPS: Ingenic: Add Halley2 development board support PrasannaKumar Muralidharan
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=20180307151025.GP4197@saruman \
--to=jhogan@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dom.peklo@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=paul@crapouillou.net \
--cc=prasannatsmkumar@gmail.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.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.