Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #52403 > unrolled thread

Bug#812540: Add ARCH_HISI for Lemaker HiKey support

Back to article view | Back to linux.debian.kernel

Contents

  Bug#812540: Add ARCH_HISI for Lemaker HiKey support Kilian Krause <kilian@debian.org> - 2016-01-24 21:30 +0100
    Bug#812540: Add ARCH_HISI for Lemaker HiKey support Ian Campbell <ijc@debian.org> - 2016-01-25 11:10 +0100
      Bug#812540: Add ARCH_HISI for Lemaker HiKey support Martin Michlmayr <tbm@cyrius.com> - 2016-03-11 01:40 +0100
        Bug#812540: Add ARCH_HISI for Lemaker HiKey support Vagrant Cascadian <vagrant@debian.org> - 2016-03-12 05:10 +0100
          Bug#812540: Add ARCH_HISI for Lemaker HiKey support Ian Campbell <ijc@debian.org> - 2016-03-12 12:30 +0100
            Bug#812540: Add ARCH_HISI for Lemaker HiKey support Vagrant Cascadian <vagrant@debian.org> - 2016-03-12 18:10 +0100
              Bug#812540: Add ARCH_HISI for Lemaker HiKey support Ian Campbell <ijc@debian.org> - 2016-03-13 19:00 +0100
                Bug#812540: Add ARCH_HISI for Lemaker HiKey support Vagrant Cascadian <vagrant@debian.org> - 2016-04-11 02:50 +0200
                  Bug#812540: [arm64] Additional modules for HiKey support Vagrant Cascadian <vagrant@debian.org> - 2016-04-14 19:50 +0200
    Processed: [arm64] Additional modules for HiKey support owner@bugs.debian.org (Debian Bug Tracking System) - 2016-04-14 19:50 +0200

#52403 — Bug#812540: Add ARCH_HISI for Lemaker HiKey support

Package: linux
Version: 4.3.3-7
Severity: wishlist
Tags: d-i

Dear kernel maintainers,

while trying to get a d-i booted on a Lemaker HiKey, tbm pointed out
that ARCH_HISI is not (yet) activated on linux.

Please enable it so we can add HiKey support to Debian.

TIA!

Best,
Kilian

[toc] | [next] | [standalone]

#52410

On Sun, 2016-01-24 at 21:21 +0100, Kilian Krause wrote:
> Package: linux
> Version: 4.3.3-7
> Severity: wishlist
> Tags: d-i
> 
> Dear kernel maintainers,
> 
> while trying to get a d-i booted on a Lemaker HiKey, tbm pointed out
> that ARCH_HISI is not (yet) activated on linux.
> 
> Please enable it so we can add HiKey support to Debian.

I suppose it will need more than just ARCH_HISI. Are you able to identify
the full set of options (e.g. drivers and such) which are needed to make
useful Lemaker support? If so I'd appreciate it (if not I can probably try
and dig those out myself, but it might take me a while to around to it).

Lemaker HiKey is the 96boards thing, right? Good to finally see that
hitting upstream, was it properly supported in 4.3.x or should this change
be made in experimental (currently 4.4.x)?

Thanks,
Ian.

[toc] | [prev] | [next] | [standalone]

#53177

* Ian Campbell <ijc@debian.org> [2016-01-25 09:57]:
> > Please enable it so we can add HiKey support to Debian.
> 
> I suppose it will need more than just ARCH_HISI. Are you able to identify
> the full set of options (e.g. drivers and such) which are needed to make
> useful Lemaker support? If so I'd appreciate it (if not I can probably try
> and dig those out myself, but it might take me a while to around to it).

This might be a good starting point:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1098644.html

-- 
Martin Michlmayr
http://www.cyrius.com/

[toc] | [prev] | [next] | [standalone]

#53183

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-10, Martin Michlmayr wrote:
> * Ian Campbell <ijc@debian.org> [2016-01-25 09:57]:
>> I suppose it will need more than just ARCH_HISI. Are you able to identify
>> the full set of options (e.g. drivers and such) which are needed to make
>> useful Lemaker support? If so I'd appreciate it (if not I can probably try
>> and dig those out myself, but it might take me a while to around to it).

Most drivers aren't even available in 4.4.x, and some aren't even in
4.5.x yet. From a breif glance, the dts files for
arch/arm64/boot/dts/hisilicon/hi6220*, don't look to contain support for
much more than the CPU, memory and serial...


> This might be a good starting point:
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1098644.html

Reading that patch, I'm guessing the following are available and
possibly needed or desired, though possibly may require device-tree
patches as well:

available in 4.4.x:

CONFIG_ARCH_HISI=y
CONFIG_POWER_RESET_HISI=y
CONFIG_HISI_THERMAL=m
CONFIG_MMC_DW=m
CONFIG_MMC_DW_K3=m
CONFIG_I2C_DESIGNWARE_PLATFORM=m

available in 4.5.x:

CONFIG_COMMON_RESET_HI6220=m
CONFIG_PHY_HI6220_USB=m

linux-next tag next-20160311:

CONFIG_HI6220_MBOX=m
CONFIG_REGULATOR_HI655X=m


Will build a few test kernels and report back...


live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#53185

On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote:
> On 2016-03-10, Martin Michlmayr wrote:
> > * Ian Campbell <ijc@debian.org> [2016-01-25 09:57]:
> >> I suppose it will need more than just ARCH_HISI. Are you able to
> identify
> >> the full set of options (e.g. drivers and such) which are needed
> to make
> >> useful Lemaker support? If so I'd appreciate it (if not I can
> probably try
> >> and dig those out myself, but it might take me a while to around
> to it).
> 
> Most drivers aren't even available in 4.4.x, and some aren't even in
> 4.5.x yet. From a breif glance, the dts files for
> arch/arm64/boot/dts/hisilicon/hi6220*, don't look to contain support
> for
> much more than the CPU, memory and serial...
> 
> 
> > This might be a good starting point:
> > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg109864
> 4.html
> 
> Reading that patch, I'm guessing the following are available and
> possibly needed or desired, though possibly may require device-tree
> patches as well:
> 
> available in 4.4.x:
> 
> CONFIG_ARCH_HISI=y
> CONFIG_POWER_RESET_HISI=y
> CONFIG_HISI_THERMAL=m
> CONFIG_MMC_DW=m
> CONFIG_MMC_DW_K3=m
> CONFIG_I2C_DESIGNWARE_PLATFORM=m
> 
> available in 4.5.x:
> 
> CONFIG_COMMON_RESET_HI6220=m
> CONFIG_PHY_HI6220_USB=m
> 
> linux-next tag next-20160311:
> 
> CONFIG_HI6220_MBOX=m
> CONFIG_REGULATOR_HI655X=m
> 
> 
> Will build a few test kernels and report back...

Thanks, for things other than the ones listed above the ones I'd be
most curious about would be serial and networking (wifi only on this
platform IIRC). Both of those could possibly be supported already via
existing generic drivers, I've no idea...

Ian.

[toc] | [prev] | [next] | [standalone]

#53186

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-12, Ian Campbell wrote:
> On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote:
>> On 2016-03-10, Martin Michlmayr wrote:
>> > * Ian Campbell <ijc@debian.org> [2016-01-25 09:57]:
>> Most drivers aren't even available in 4.4.x, and some aren't even in
>> 4.5.x yet. From a breif glance, the dts files for
>> arch/arm64/boot/dts/hisilicon/hi6220*, don't look to contain support
>> for
>> much more than the CPU, memory and serial...
>> 
>> 
>> > This might be a good starting point:
>> > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg109864
>> 4.html
>> 
>> Reading that patch, I'm guessing the following are available and
>> possibly needed or desired, though possibly may require device-tree
>> patches as well:
>> 
>> available in 4.4.x:
>> 
>> CONFIG_ARCH_HISI=y
>> CONFIG_POWER_RESET_HISI=y
>> CONFIG_HISI_THERMAL=m
>> CONFIG_MMC_DW=m
>> CONFIG_MMC_DW_K3=m
>> CONFIG_I2C_DESIGNWARE_PLATFORM=m
>> 
>> available in 4.5.x:
>> 
>> CONFIG_COMMON_RESET_HI6220=m
>> CONFIG_PHY_HI6220_USB=m
>> 
>> linux-next tag next-20160311:
>> 
>> CONFIG_HI6220_MBOX=m
>> CONFIG_REGULATOR_HI655X=m
>> 
>> 
>> Will build a few test kernels and report back...
>
> Thanks, for things other than the ones listed above the ones I'd be
> most curious about would be serial and networking (wifi only on this
> platform IIRC). Both of those could possibly be supported already via
> existing generic drivers, I've no idea...

Not sure about WIFI, but serial seems already enabled:

  CONFIG_SERIAL_AMBA_PL011=y
  CONFIG_SERIAL_AMBA_PL011_CONSOLE=y

arch/arm64/boot/dts/hisilicon/hi6220.dtsi:

        uart0: uart@f8015000 {    /* console */
            compatible = "arm,pl011", "arm,primecell";
            reg = <0x0 0xf8015000 0x0 0x1000>;
            interrupts = <GIC_SPI 36 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ao_ctrl HI6220_UART0_PCLK>,
                 <&ao_ctrl HI6220_UART0_PCLK>;
            clock-names = "uartclk", "apb_pclk";
        };


live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#53197

On Sat, 2016-03-12 at 09:00 -0800, Vagrant Cascadian wrote:
> On 2016-03-12, Ian Campbell wrote:
> > On Fri, 2016-03-11 at 20:03 -0800, Vagrant Cascadian wrote:
> >> On 2016-03-10, Martin Michlmayr wrote:
> >> > * Ian Campbell <ijc@debian.org> [2016-01-25 09:57]:
> >> Most drivers aren't even available in 4.4.x, and some aren't even
> in
> >> 4.5.x yet. From a breif glance, the dts files for
> >> arch/arm64/boot/dts/hisilicon/hi6220*, don't look to contain
> support
> >> for
> >> much more than the CPU, memory and serial...
> >> 
> >> 
> >> > This might be a good starting point:
> >> > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg109
> 864
> >> 4.html
> >> 
> >> Reading that patch, I'm guessing the following are available and
> >> possibly needed or desired, though possibly may require device-
> tree
> >> patches as well:
> >> 
> >> available in 4.4.x:
> >> 
> >> CONFIG_ARCH_HISI=y
> >> CONFIG_POWER_RESET_HISI=y
> >> CONFIG_HISI_THERMAL=m
> >> CONFIG_MMC_DW=m
> >> CONFIG_MMC_DW_K3=m
> >> CONFIG_I2C_DESIGNWARE_PLATFORM=m
> >> 
> >> available in 4.5.x:
> >> 
> >> CONFIG_COMMON_RESET_HI6220=m
> >> CONFIG_PHY_HI6220_USB=m
> >> 
> >> linux-next tag next-20160311:
> >> 
> >> CONFIG_HI6220_MBOX=m
> >> CONFIG_REGULATOR_HI655X=m
> >> 
> >> 
> >> Will build a few test kernels and report back...
> >
> > Thanks, for things other than the ones listed above the ones I'd be
> > most curious about would be serial and networking (wifi only on
> this
> > platform IIRC). Both of those could possibly be supported already
> via
> > existing generic drivers, I've no idea...
> 
> Not sure about WIFI, but serial seems already enabled:
> 
>   CONFIG_SERIAL_AMBA_PL011=y
>   CONFIG_SERIAL_AMBA_PL011_CONSOLE=y

That makes sense, thanks for the info. Since MMC + serial in 4.4 is a
basically useful thing (and I'm hoping the WiFi is some preexisting
driver too) this seemed like a useful set of stuff to enable. So I have
done so in git.

Ian.

[toc] | [prev] | [next] | [standalone]

#53540

[Multipart message — attachments visible in raw view] — view raw

On 2016-03-13, Ian Campbell wrote:
> That makes sense, thanks for the info. Since MMC + serial in 4.4 is a
> basically useful thing (and I'm hoping the WiFi is some preexisting
> driver too) this seemed like a useful set of stuff to enable. So I have
> done so in git.

Thanks for enabling it!

I was able to get it to boot with both 4.4 and 4.5 to an initramfs
prompt and a serial console, but MMC support still needs to be enabled
in the device-tree, along with USB, wireless, and just about anything
else you might actually want to use. :)

For wireless it needs additional drivers enabled in the kernel:

  # on 4.4.x
  CONFIG_WL_TI=y
  # on 4.5+
  CONFIG_WLAN_VENDOR_TI=y

  CONFIG_WL18XX=m

Still need these drivers enabled in 4.5.x:

  CONFIG_COMMON_RESET_HI6220=m
  CONFIG_PHY_HI6220_USB=m

And when the time comes, these in 4.6+:

  CONFIG_HI6220_MBOX=m

  # while this is present in mainline, it seems to depend on
  # MFD_HI655X_PMIC which isn't yet present... so hrm.
  CONFIG_REGULATOR_HI655X=m


live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#53610 — Bug#812540: [arm64] Additional modules for HiKey support

[Multipart message — attachments visible in raw view] — view raw

Control: clone 812540 -1
Control: retitle -1 [arm64] Additional modules for HiKey support
Control: severity -1 wishlist

On 2016-04-10, Vagrant Cascadian wrote:
> I was able to get it to boot with both 4.4 and 4.5 to an initramfs
> prompt and a serial console, but MMC support still needs to be enabled
> in the device-tree, along with USB, wireless, and just about anything
> else you might actually want to use. :)

I'm not sure what the policy on enabling modules for boards that don't
yet have the corresponding device-tree entries, but it would be nice to
have all of the modules mentioned below enabled, so that when
device-tree support is available for HiKey (or other boards) upstream,
the debian kernel packages will "just work". It also makes it easier to
use a user-supplied device-tree without having to recompile the kernel.


> For wireless it needs additional drivers enabled in the kernel:
...
>   # on 4.5+
>   CONFIG_WLAN_VENDOR_TI=y
>
>   CONFIG_WL18XX=m
>
> Still need these drivers enabled in 4.5.x:
>
>   CONFIG_COMMON_RESET_HI6220=m
>   CONFIG_PHY_HI6220_USB=m
>
> And when the time comes, these in 4.6+:
>
>   CONFIG_HI6220_MBOX=m
>
>   # while this is present in mainline, it seems to depend on
>   # MFD_HI655X_PMIC which isn't yet present... so hrm.
>   CONFIG_REGULATOR_HI655X=m


Thanks!


live well,
  vagrant

[toc] | [prev] | [next] | [standalone]

#53611 — Processed: [arm64] Additional modules for HiKey support

Processing control commands:

> clone 812540 -1
Bug #812540 {Done: Ben Hutchings <ben@decadent.org.uk>} [linux] Add ARCH_HISI for Lemaker HiKey support
Bug 812540 cloned as bug 821027
> retitle -1 [arm64] Additional modules for HiKey support
Bug #821027 {Done: Ben Hutchings <ben@decadent.org.uk>} [linux] Add ARCH_HISI for Lemaker HiKey support
Changed Bug title to '[arm64] Additional modules for HiKey support' from 'Add ARCH_HISI for Lemaker HiKey support'.
> severity -1 wishlist
Bug #821027 {Done: Ben Hutchings <ben@decadent.org.uk>} [linux] [arm64] Additional modules for HiKey support
Ignoring request to change severity of Bug 821027 to the same value.

-- 
812540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812540
821027: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821027
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web