From: Guenter Roeck <linux@roeck-us.net>
To: Emil Renner Berthing <kernel@esmil.dk>,
Drew Fustini <drew@beagleboard.org>
Cc: Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Samin Guo <samin.guo@starfivetech.com>,
linux-hwmon@vger.kernel.org,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
linux-doc@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] hwmon: Add StarFive JH7100 temperature sensor
Date: Sun, 1 Aug 2021 13:29:50 -0700 [thread overview]
Message-ID: <f09e323b-90f3-8fd6-e5ba-e3c5ac823dc6@roeck-us.net> (raw)
In-Reply-To: <CANBLGcyhKYwsLOwaO=BOhaCzP0T2CqKruJZexypRAY3HmEJUMA@mail.gmail.com>
On 8/1/21 1:19 PM, Emil Renner Berthing wrote:
> On Wed, 28 Jul 2021 at 19:05, Emil Renner Berthing <kernel@esmil.dk> wrote:
>> On Wed, 28 Jul 2021 at 18:54, Guenter Roeck <linux@roeck-us.net> wrote:
>>> On 7/26/21 10:18 AM, Emil Renner Berthing wrote:
>>>> This adds a driver for the temperature sensor on the JH7100, a RISC-V
>>>> SoC by StarFive Technology Co. Ltd., and most likely also the upcoming
>>>> JH7110 version.
>>>>
>>>> The SoC is used on the BeagleV Starlight board:
>>>> https://github.com/beagleboard/beaglev-starlight
>>>>
>>>> Support for this SoC is not yet upstreamed, but is actively worked on,
>>>> so it should only be a matter of time before that happens.
>>>>
>>>
>>> Hmm, makes me wonder if I should apply the series now or later,
>>> when the chip is actually supported by the kernel. Comments/thoughts ?
>>>
>>> Guenter
>>
>> I'd of course love if it was applied now. That would at least mean
>> fewer patches to rebase when keeping the beaglev patches [1] up to
>> date, and I'd be very surprised if SoC support doesn't make it
>> upstream eventually. But I'd also fully understand the position that
>> this only makes sense to add when support for the SoC is upstream too.
>> I'm adding Drew, as he might have something to say about this.
>
> Hi Guenter,
>
> Things have changed. The BeagleBoard.org foundation is no longer
> planning to make any further boards using the JH7100 or upcoming
> JH7110 SoCs from StarFive. I still think support for the JH7100 will
> make it upstream eventually, but I'm no longer confident enough to
> recommend merging this before there are more concrete plans for the
> SoC. So thanks for the reviews. I'll repost it when I think it's time
> to consider it for upstream again.
>
Thanks for the update.
Guenter
prev parent reply other threads:[~2021-08-01 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:18 [PATCH v3 0/2] hwmon: Add StarFive JH7100 temperature sensor Emil Renner Berthing
2021-07-26 17:18 ` [PATCH v3 1/2] dt-bindings: hwmon: add starfive,jh7100-temp bindings Emil Renner Berthing
2021-07-26 17:18 ` [PATCH v3 2/2] hwmon: (sfctemp) Add StarFive JH7100 temperature sensor Emil Renner Berthing
2021-07-28 16:54 ` [PATCH v3 0/2] hwmon: " Guenter Roeck
2021-07-28 17:05 ` Emil Renner Berthing
2021-08-01 20:19 ` Emil Renner Berthing
2021-08-01 20:29 ` Guenter Roeck [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=f09e323b-90f3-8fd6-e5ba-e3c5ac823dc6@roeck-us.net \
--to=linux@roeck-us.net \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=jdelvare@suse.com \
--cc=kernel@esmil.dk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=samin.guo@starfivetech.com \
/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;
as well as URLs for NNTP newsgroup(s).