From: Julian Winkler <julian.winkler1@web.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
Hans de Goede <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH] intel_scu_pcidrv: add back PCI id for Medfield
Date: Mon, 17 Apr 2023 15:02:24 +0200 [thread overview]
Message-ID: <a52ab618-97ea-04ea-01e4-ecb673f45f09@web.de> (raw)
In-Reply-To: <CAHp75VfFptZcJn7c_a2GLnSqJDXBwvUqWmu9Wb19a3VvwXJS5A@mail.gmail.com>
On 17.04.23 12:16, Andy Shevchenko wrote:
> On Mon, Apr 17, 2023 at 1:11 PM Hans de Goede <hdegoede@redhat.com> wrote:
>> +Cc Andy, Mika,
>
> Thanks for Cc'ing me.
>
>> On 4/16/23 17:49, Julian Winkler wrote:
>>> This id was removed in b47018a778c1a18cbc98b4a11936dec4f8c4bb7b, saying it
>>> is only used on Moorestown, but apparently the same id is also used on
>>> Medfield.
>>>
>>> Tested on the Medfield based Motorola RAZR i smartphone.
>
> Wow! This is surprising.
> Can you tell more about your test environment? What is the Linux
> kernel version in use and what is the userspace (AOSP, Buildroot,
> Yocto, custom)? If custom, more details would be nice to hear.
The test enviroment is postmarketOS. You can find more details on the
Wiki page
https://wiki.postmarketos.org/wiki/Motorola_RAZR_i_(XT890)_(motorola-smi)
>>> Signed-off-by: Julian Winkler <julian.winkler1@web.de>
>>
>> Hmm, so this is a former SFI platform, from your:
>> https://lore.kernel.org/all/20230223060107.23029-1-julian.winkler1@web.de/
>>
>> patch I guess the plan is to use some custom bootloader
>> and then use x86 with devicetree support to replace SFI ?
>
> That would also be nice to hear in detail. With other Intel MID
> platforms the decision was made to pursue ACPI (and U-Boot, as an
> example) supports that for Intel Merrifield platform.
I boot a 5.10 kernel, which still has SFI support, and from there I can
boot latest mainline kernel with petitboot, kexec and devicetree.
>> Do you already have this working ?
>>
>> Sorry for all the questions for what is just a simple PCI-id
>> addition. I guess I'm worried this is just the tip of
>> the iceberg for getting medfield support back into
>> the kernel and I'm a bit worried about how much maintenance
>> work this will cause.
>>
>> E.g. also see commit e1da811218d2dc ("drm/gma500: Remove Medfield support")
>> which I guess you will want to see reverted too ?
>>
>> That is an example of a lot more code to bring back
>> then just a single PCI-id addition.
>>
>> Don't get me wrong I'm all for supporting older hw
>> if there are users who are interested in actively
>> maintaining support for it. I just want to get a feel
>> of the amount of work this is going to involve.
>>
>> Andy, Mika, any remarks ?
>
> I'm not against a patch if it helps existing users, but we need to
> understand first if it will be really helpful for upstream (taking
> into account 32-bit Intel MID support removal).
My downstream kernel tree can be seen here:
https://gitlab.com/julianwi/linux-intel-medfield. Indeed, I needed to
bring back some removed code to get the display working, but even
without display driver, old smartphones can be used as a server or
Raspberry Pi replacement.
next prev parent reply other threads:[~2023-04-17 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 15:49 [PATCH] intel_scu_pcidrv: add back PCI id for Medfield Julian Winkler
2023-04-17 10:11 ` Hans de Goede
2023-04-17 10:16 ` Andy Shevchenko
2023-04-17 13:02 ` Julian Winkler [this message]
2023-04-25 9:03 ` Hans de Goede
2023-04-27 7:36 ` Julian Winkler
2023-04-25 19:02 ` Andy Shevchenko
2023-04-27 8:06 ` Julian Winkler
2023-04-27 10:33 ` Andy Shevchenko
2023-04-25 15:03 ` Hans de Goede
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=a52ab618-97ea-04ea-01e4-ecb673f45f09@web.de \
--to=julian.winkler1@web.de \
--cc=andy.shevchenko@gmail.com \
--cc=hdegoede@redhat.com \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@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