linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: ChiYuan Huang <u0084500@gmail.com>,
	djrscally@gmail.com, hdegoede@redhat.com, markgross@kernel.org,
	lgirdwood@gmail.com, mcoquelin.stm32@gmail.com,
	alexandre.torgue@foss.st.com, yangyingliang@huawei.com,
	gene_chen@richtek.com, chiaen_wu@richtek.com,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	ChiYuan Huang <cy_huang@richtek.com>
Subject: Re: [PATCH v2] regulator: core: Use different devices for resource allocation and DT lookup
Date: Wed, 14 Dec 2022 13:32:18 +0000	[thread overview]
Message-ID: <Y5nQYom7SsbFnir+@sirena.org.uk> (raw)
In-Reply-To: <be56fd97-08b5-8a7a-2630-371c83dcab18@samsung.com>


[-- Attachment #1.1: Type: text/plain, Size: 1389 bytes --]

On Tue, Dec 13, 2022 at 11:23:01PM +0100, Marek Szyprowski wrote:
> On 13.12.2022 17:32, Mark Brown wrote:

> > Thanks for jumping on this so quickly!  Marek, are these boards (or
> > similar ones) generally available?  They seem great at showing up issues
> > so it'd be good if I could get them into my CI and spot problems earlier
> > (or something like kernelci.org would be about as good)?

> Well, they are quite old, but I've seen some used ones on eBay. Just 
> look for "Samsung Chomebook XE503C12" (Peach-Pit) or XE503C32 (Peach-Pi, 
> very rare).

> Getting it integrated into the CI requires a bit of manual work. You 
> have to solder UART lines to the test points on the motherboard. The 
> board can be fully controlled via so called Embedded Controller, what in 
> practice means that you can turn power on/off by sending commands to the 
> dedicated EC UART. The kernel console UART uses 1.8V, while the EC UART 
> - 3.3V. Let me know if you need more details.

Ah, oh dear - I'm afraid my soldering ability isn't up to that sort of
modification.

> Peach-Pi was used on kernelci.org some time ago, but I have no idea what 
> has happened to it.

I suspect it might've fallen off the end of the ChromeOS support window 
and got pulled, I'll see if I can find out.  Perhaps there's some
modified boards kicking about that didn't get thrown out.

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

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-12-14 13:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221213113259eucas1p1c224898772bc5e59de90c1aa65a34de0@eucas1p1.samsung.com>
2022-12-06  7:22 ` [PATCH v2] regulator: core: Use different devices for resource allocation and DT lookup cy_huang
2022-12-08 14:09   ` Mark Brown
2022-12-13 11:32   ` Marek Szyprowski
2022-12-13 14:19     ` ChiYuan Huang
2022-12-13 14:29       ` Marek Szyprowski
2022-12-13 16:32         ` Mark Brown
2022-12-13 22:23           ` Marek Szyprowski
2022-12-14 13:32             ` Mark Brown [this message]
2022-12-14  0:35         ` ChiYuan Huang

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=Y5nQYom7SsbFnir+@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=chiaen_wu@richtek.com \
    --cc=cy_huang@richtek.com \
    --cc=djrscally@gmail.com \
    --cc=gene_chen@richtek.com \
    --cc=hdegoede@redhat.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=m.szyprowski@samsung.com \
    --cc=markgross@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=u0084500@gmail.com \
    --cc=yangyingliang@huawei.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).