From: Peter Griffin <peter.griffin@linaro.org>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
Will McVicker <willmcvicker@google.com>
Subject: Re: UFS storage support for Tensor/GS101?
Date: Thu, 4 Apr 2024 13:31:40 +0100 [thread overview]
Message-ID: <CADrjBPrLnowwe+GNLmpRJjMUsCv3pqcadsSAhWQE5KPLfVVcCw@mail.gmail.com> (raw)
In-Reply-To: <20240207015234.GD35324@sol.localdomain>
Hi Eric,
On Wed, 7 Feb 2024 at 01:52, Eric Biggers <ebiggers@kernel.org> wrote:
>
> Hi Peter,
>
> On Tue, Feb 06, 2024 at 05:09:13PM +0000, Peter Griffin wrote:
> > Hi Eric,
> >
> > + Will
> >
> > On Tue, 6 Feb 2024 at 03:45, Eric Biggers <ebiggers@kernel.org> wrote:
> > >
> > > Hi Peter! Thanks for all the hard work you've been doing on upstreaming support
> > > for Tensor/GS101. I've tested that the latest upstream kernel is now able to
> > > boot to a serial console on Pixel 6.
> >
> > Thanks for testing :)
> > >
> > > I'm wondering if you have any plans to upstream support for the UFS storage on
> > > that platform? It should be able to use the already-upstream
> > > drivers/ufs/host/ufs-exynos.c driver, but changes may be required; I'm not sure
> > > how many. I'm interested in this mainly because I'd like to upstream some
> > > patches related to inline encryption, and that depends on UFS storage working.
> > >
> > > I'm interested in helping with this, but I wanted to check to see if you know
> > > about any existing plans first.
> >
> > We certainly want to add support for UFS upstream, and if you can help
> > out with enabling it that would be great! It would free us up to work
> > on enabling something else in parallel. From a first pass analysis of
> > the downstream UFS code it looks like ufs phy driver likely needs the
> > most attention.
> >
> > The last UFS dependency (that I'm aware of) that is missing currently
> > is clock support for cmu_hsi2 (which I was planning on working on as
> > my next task). Also the UFS phy accesses PMU registers so that will
> > require my exynos-pmu [1] series but that is hopefully close to being
> > merged.
> >
> > So I think we are quite close to having all the UFS dependencies in
> > place. Shall I ping you once I have some code for cmu_hsi2, and
> > hopefully that should be enough for you to start working on the UFS
> > driver and phy?
> >
> > Thanks,
> >
> > Peter
>
> Yes, let me know as soon as you have some code for cmu_hsi2, and I'll try to get
> UFS working. I don't know how hard it will be, though, so it's possible I'll
> need help from others.
I just posted an initial series that adds the cmu_hsi2 clocks, UFS
controller glue
and UFS phy for GS101 (your on cc). With that series applied, UFS link comes up
and you can mount flash partitions etc.
Hopefully that is enough to unblock you so you can start on the inline
encryption
feature. Let me know how you get on :)
Thanks,
Peter.
prev parent reply other threads:[~2024-04-04 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 3:45 UFS storage support for Tensor/GS101? Eric Biggers
2024-02-06 17:09 ` Peter Griffin
2024-02-07 1:52 ` Eric Biggers
2024-02-07 18:04 ` William McVicker
2024-02-07 20:09 ` Bart Van Assche
2024-04-04 12:31 ` Peter Griffin [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=CADrjBPrLnowwe+GNLmpRJjMUsCv3pqcadsSAhWQE5KPLfVVcCw@mail.gmail.com \
--to=peter.griffin@linaro.org \
--cc=ebiggers@kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=willmcvicker@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).