From: l.stach@pengutronix.de (Lucas Stach)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/7] Hummingboard2 improvements
Date: Mon, 10 Jul 2017 10:52:46 +0200 [thread overview]
Message-ID: <1499676766.2924.6.camel@pengutronix.de> (raw)
In-Reply-To: <CABdtJHsGKrZ4R-kcikc9dsrO-CrZpRXzNEmQT4WgKJ=UZfDRCg@mail.gmail.com>
Hi Jon,
Am Sonntag, den 09.07.2017, 06:42 +0200 schrieb Jon Nettleton:
> On Sun, Jul 9, 2017 at 6:39 AM, Jon Nettleton <jon@solid-run.com> wrote:
> >
> >
> >
> > On Sat, Jul 8, 2017 at 3:59 PM, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> >>
> >> On Sat, Jun 24, 2017 at 08:30:31AM +0100, Russell King - ARM Linux wrote:
> >> > On Fri, Jun 23, 2017 at 06:15:14PM +0200, Lucas Stach wrote:
> >> > > Hi Russell,
> >> > >
> >> > > it seems this is making no progress. If you don't mind I'm going to pick
> >> > > up the patches from you hb2 branch and submit the whole series to Shawn,
> >> > > so we can finally get things merged. Are you okay with this?
> >> >
> >> > If you remember from the reviews back in January of my patch set, Jon
> >> > Nettleton promised to send me a replacement set of DT files that were
> >> > properly licensed and updated along the lines of your patches in April.
> >> > I'm still waiting...
> >>
> >> I've chased Jon a couple more times since (once today), and I'm feeling
> >> that we're not getting anywhere. I've now told him that we (SolidRun/
> >> myself) are in danger of having this work replaced by others. So, I'm
> >> now adding Rabeeh to this thread.
> >>
> >>
>
> Besides the licensing there are still a number of bugs that exist for
> the device-tree files as they stand. Most notably using the standard
> regulator code for the SDHC device causes a hang on reboot with some
> UHS cards.
What's the issue here? Is the bootloader not coming up, or does the
kernel hang at boot?
> Additionally we need to bring in the support for the SOM rev1.5 which
> has been waiting on the TTY slave devices infrastructure to land. We
> have been trying to come up with a better solution than duplicating
> all our device-tree files with a som revision however there doesn't
> seem to be. I would prefer to bring all the support in at once since
> we are only shipping rev 1.5 soms at this point
What's the difference between the old and new SoMs? Can we patch the DTs
from the bootloader instead of introducing more variants?
Frankly this whole situation is very bad. I have this Hummingboard2
lying around for 1.5 years now, with no mainline support available. With
the reasoning above it doesn't seem like this is going to change in the
near future, as perfect is the enemy of good.
Is there anything we can do help out with this?
Regards,
Lucas
next prev parent reply other threads:[~2017-07-10 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 14:36 [RFC PATCH 0/7] Hummingboard2 improvements Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 1/7] ARM: dts: imx6*-hummingboard2: fix formatting Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 2/7] ARM: dts: imx6*-hummingboard2: add SGTL5000 VDDD supply Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 3/7] ARM: dts: imx6*-hummingboard2: remove LDB node Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 4/7] ARM: dts: imx6*-hummingboard2: fix PCIe reset polarity Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 5/7] ARM: dts: imx6*-hummingboard2: remove non-mainline property from RTC Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 6/7] ARM: dts: imx6*-hummingboard2: remove redundant PWM disables Lucas Stach
2017-04-08 14:36 ` [RFC PATCH 7/7] ARM: dts: imx6*-hummingboard2: rework regulators Lucas Stach
2017-06-23 16:15 ` [RFC PATCH 0/7] Hummingboard2 improvements Lucas Stach
2017-06-24 7:30 ` Russell King - ARM Linux
2017-07-08 13:59 ` Russell King - ARM Linux
[not found] ` <CABdtJHutd5v4onVMMZdufnutzDWt5R3RE3XxicfHsTZkNUYXCg@mail.gmail.com>
2017-07-09 4:42 ` Jon Nettleton
2017-07-10 8:52 ` Lucas Stach [this message]
2017-07-10 9:29 ` Jon Nettleton
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=1499676766.2924.6.camel@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox