Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Henrik Grimler <henrik@grimler.se>
To: Kian <kianprogramer@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Samsung Galaxy J7 Pro (j7y17lte) — Upstream Linux support
Date: Thu, 1 Oct 2026 11:58:44 +0200	[thread overview]
Message-ID: <20261001095838.GA26093@localhost> (raw)
In-Reply-To: <CAC-nSOxO_9tSE8jNGGQZKPtiKPq0qn2sgGWppzD_8yu1q=Wamg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 5424 bytes --]

Hi Kian,

On Thu, Oct 01, 2026 at 10:33:42AM +0330, Kian wrote:
> Hello,
> 
> I am reaching out regarding mainline Linux support for the Samsung
> Galaxy J7 Pro (SM-J730F, j7y17lte), which is based on the Samsung
> Exynos 7870 SoC.
> 
> The Exynos 7870 already has upstream Linux support and ongoing
> community development, including Device Tree support for the SoC and
> several devices based on it.
> 
> There have also been several community projects and attempts
> specifically targeting the J7 Pro. For example, there are existing
> Device Tree sources such as exynos7870-j7y17lte.dts, previous attempts
> to boot newer Linux kernels on the device, and Linux/postmarketOS work
> targeting the actual J7 Pro hardware.
> 
> These projects are useful starting points, but each of them has its
> own limitations, missing functionality, or unresolved issues,

I think you are misunderstanding the community projects. They are
missing features or have unresolved issues because no one has had
time, or the skills, or the interest, to work on the
features/issues. Issues or regressions happen with mainline linux as
well, and there is no guarantee that anyone has time or interest to
discover and investigate issues for older devices here
either.

> and none of them provides complete upstream support for the J7 Pro.

"complete upstream support" would be the (un-achievable?) end-goal, of
course none of them prove complete upstream support.

> I can provide links to these projects and repositories so that the
> existing work can be reviewed and compared.
> 
> Rather than creating yet another unofficial downstream kernel or
> another separate community project with its own limitations,

Ok, but how will you test your patches? It seems a lot easier to test
the kernel together with a community project rather than writing your
own initfs and rootfs and essentially inventing yet another community
project in the process.

> I would like to try to bring the existing work together and work
> toward proper upstream Linux support for the device.

PostmarketOS (now re-branded as Nura [1]) encourages contributors to
send their patches upstream, a lot of time has been spent on writing
wiki pages about the upstreaming process, and creating a mainlining
guide [2, 3]. I suggest you read the guide and reach out to the other
people working on exynos7xxx devices.

> Would someone familiar with the Exynos 7870 platform and Samsung
> Device Trees be interested in reviewing the existing J7 Pro work and
> assessing what is still required for mainline support?

Rather than thinking about what is missing you should start testing a
small barebone .dts for your device (maybe with uart/serial and/or
framebuffer support and not much else), and add more features when you
have had the time to properly test and verify them. This is where
community projects are useful, you can collaborate with others that
are working on the same or similar devices and test&develop features
together.

> I own a physical SM-J730F and have access to the actual device for
> development and testing. I can provide the links to the existing
> community projects, Device Tree sources, repositories, and other
> relevant work.
> 
> I am willing to do anything that is reasonably within my ability to
> help with the upstreaming effort. I can perform hardware testing,
> collect boot logs and dmesg output, investigate hardware and Device
> Tree information, reproduce issues, test kernel and Device Tree
> changes, test patches on the actual device, and provide reproducible
> test results. If additional information or specific tests are needed,
> I am also willing to carry them out and learn whatever is necessary to
> help with the development process.

Sounds great, only thing missing is then to create the dts for the
device, and probably add support for your device to some drivers. Most
likely no one here will prepare patches for you, so this is a great
opportunity for you to learn how to do those things.

Again, I suggest you get involved with a community project and learn
from, and together with, the other people interested in adding support
upstream for similar devices. Nura(/PostmarketOS) for example has an
active exynos-arm64 community that work on exynos7xxx and other arm64
SOCs, please check out their matrix chat [4].

[1] https://nura.eco/blog/2026/09/27/nura-rename/
[2] https://wiki.nura.eco/wiki/Mainlining
[3] https://wiki.nura.eco/wiki/Mainlining_Guide
[4] https://matrix.to/#/#exynos-arm64-mainline:nope.chat

Best regards,
Henrik Grimler

> I do not want to simply create another unofficial project for the J7
> Pro. My goal is to make use of the work that already exists, identify
> what is missing or needs to be fixed, and help move the device toward
> a clean and maintainable upstream implementation.
> 
> If there is interest in working on this, I can provide the relevant
> project and repository links, Device Tree sources, logs, and any other
> hardware information I have available.
> 
> I would be very interested in helping bring the J7 Pro into the
> upstream Linux ecosystem, and I am willing to contribute wherever I
> can.
> 
> Thank you for your time and for your work on Samsung Exynos support in
> the Linux kernel.
> 
> Best regards,
> 
> A J7 Pro owner and contributor
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 525 bytes --]

      reply	other threads:[~2026-10-01  9:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01  7:03 Samsung Galaxy J7 Pro (j7y17lte) — Upstream Linux support Kian
2026-10-01  9:58 ` Henrik Grimler [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=20261001095838.GA26093@localhost \
    --to=henrik@grimler.se \
    --cc=kianprogramer@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.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