From: xuwei5@hisilicon•com (Wei Xu)
To: linux-arm-kernel@lists•infradead.org
Subject: Older hisilicon chipsets
Date: Tue, 30 Aug 2016 09:55:33 +0100 [thread overview]
Message-ID: <57C54A05.9090601@hisilicon.com> (raw)
In-Reply-To: <7850061.5OOjP34nIO@wuerfel>
Hi Arnd, Marty
On 29/08/2016 11:54, Arnd Bergmann wrote:
> On Saturday, August 27, 2016 1:53:25 PM CEST Marty Plummer wrote:
>> On 08/27/2016 10:04 AM, Jason Cooper wrote:
>>>
>>> Ah, yes. The same device we were discussing on #mvlinux?
>>>
>> Indeed, the very same
>>>
>>> Note that I have no experience with HiSilicon. :-) However, I think
>>> it's correct to add it mach-hisi/. A quick grep shows that there is
>>> devicetree support for hisilicon SoCs (arch/arm/boot/dts/). So that
>>> means there's a *lot* less code to add under mach-hisi/.
>>>
>> The issue here is that mach-hisi/Kconfig and CONFIG_ARCH_HISI require
>> ARMv7, whereas the hi3520 has an arm1176/arm926 core, thereby being
>> ARMv6/v5
>
> No problem, just modify the dependency list for the top-level option.
>
>>> Ideally, most of it will be a devicetree. Assuming we have code for the
>>> SoC and associated drivers.
>>>
>> Yes, I've been doing some work on that already, but as I've said, unsure
>> where one should/would insert all these different things.
>
> start with getting the serial console working. debug_ll is useful for
> early bringup and should only need a patch to arch/arm/Kconfig.debug.
>
> Later you would typically use earlycon (using a stdout-path property
> in DT to point to the UART and configuration). The approximate order
> in which you need other drivers is:
>
> * drivers/irqchip (often a standard VIC or GIC)
> * drivers/clocksource
> * drivers/tty/serial/
> * drivers/clk
> * drivers/pinctrl (or drivers/gpio for simpler I/O pins)
> * drivers/mmc
> * drivers/net/ethernet
> * drivers/spi/
> * drivers/i2c/
> * drivers/mtd/
>
> In each case, look for a driver that works on your hardware first,
> or create one based on the old source if that doesn't exist upstream.
>
>>> I've added GregKH to the Cc to see if he knows of anyone currently
>>> working with Hisilicon.
>>>
>> Thanks, mayhaps someone can get even a response from Hisilicon, as I've
>> yet to recieve even that.
>
> I expect that Xu Wei will pick up the patches once they are ready to
> go in, but he probably won't have a lot of comments for your patches.
I will once they are ready.
Thanks for your kindly guiding!
Best Regards,
Wei
>
> Arnd
>
> .
>
next prev parent reply other threads:[~2016-08-30 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 0:48 Older hisilicon chipsets Marty Plummer
2016-08-27 15:04 ` Jason Cooper
2016-08-27 18:53 ` Marty Plummer
2016-08-29 10:54 ` Arnd Bergmann
2016-08-29 15:46 ` Jason Cooper
2016-08-30 8:55 ` Wei Xu [this message]
2016-08-30 14:43 ` Marty Plummer
2016-08-30 14:58 ` Jason Cooper
2016-08-30 15:36 ` Arnd Bergmann
2016-08-30 15:34 ` Wei Xu
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=57C54A05.9090601@hisilicon.com \
--to=xuwei5@hisilicon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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