From: Jisheng Zhang <jszhang@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>,
soc@kernel.org, Arnd Bergmann <arnd@arndb.de>
Cc: Conor Dooley <conor@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
Guo Ren <guoren@kernel.org>, Fu Wei <wefu@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] riscv: dts: thead: set dma-noncoherent to soc bus
Date: Wed, 18 Oct 2023 00:09:59 +0800 [thread overview]
Message-ID: <ZS6x18XEJXmB7FFL@xhacker> (raw)
In-Reply-To: <ZS1uiXORq2IRPnId@x1>
On Mon, Oct 16, 2023 at 10:10:33AM -0700, Drew Fustini wrote:
> On Thu, Sep 21, 2023 at 11:08:28AM +0100, Conor Dooley wrote:
> > On Thu, Sep 21, 2023 at 05:24:57PM +0800, Jisheng Zhang wrote:
> > > On Wed, Sep 20, 2023 at 09:36:19AM +0100, Conor Dooley wrote:
> > > > Hey Jisheng,
> > > >
> > > > On Wed, Sep 13, 2023 at 04:44:18PM +0100, Conor Dooley wrote:
> > > > > On Wed, Sep 13, 2023 at 11:15:57PM +0800, Jisheng Zhang wrote:
> > > > > > On Tue, Sep 12, 2023 at 05:27:31PM +0100, Conor Dooley wrote:
> > > > > > > On Tue, Sep 12, 2023 at 03:22:32PM +0800, Jisheng Zhang wrote:
> > > > > > > > riscv select ARCH_DMA_DEFAULT_COHERENT by default, and th1520 isn't
> > > > > > > > dma coherent, so set dma-noncoherent to reflect this fact.
> > > > > > > >
> > > > > > > > Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> > > > > > > > Tested-by: Drew Fustini <dfustini@baylibre.com>
> > > > > > > > ---
> > > > > > > >
> > > > > > > > Since v1:
> > > > > > > > - rebase on v6.6-rc1
> > > > > > > > - collect Tested-by tag
> > > > > > >
> > > > > > > Does this mean you're expecting me to take this?
> > > > > >
> > > > > > Hi Conor,
> > > > > >
> > > > > > I think I will take this and send PR to soc people. The reason
> > > > > > I send v2 is the rebasing on new rc1 and v1 wasn't in linux-riscv
> > > > > > mailist due to typo;
> > > > >
> > > > > Great, thanks. Please ask SFR to add your tree to linux-next.
> > >
> > > Hi Conor,
> > >
> > > I'm not sure how to do this. When MAINTAINERS patch is merged, send
> > > an email to Stephen Rothwell, are these steps correct?
> >
> > Sorta, yeah. You don't need to have the MAINTAINERS patch merged first
> > though, just send him a link to your tree and the branch name(s) & he
> > will include it in linux-next.
> >
> > > > I lost my main x86 box over the weekend (looks like probably a dead
> > > > motherboard), so I may have missed a response to this.
> > > >
> > > > Did you see this email? Additionally, can you add that git tree to the
> > > > maintainers entry for the thead devicetrees?
> > >
> > > I just created a tree in
> > > git://git.kernel.org/pub/scm/linux/kernel/git/jszhang/linux.git
> > >
> > > But it needs time for cgit to take place. I will send a patch
> > > once it appears.
> >
> > Looks to be there for me now. Thanks for doing this!
>
> Hi Jisheng, I'm writing the cover letter for v2 of my th1520 mmc series
> and I am wondering if this dma-noncoherent patch is in any tree yet?
Hi Drew,
I forget this patch. Thanks for reminding.
Hi Arnd
This is the only one dt fix for thead SoC, can you please pick it up
for the upcoming -rcN? I knew soc people can directly ask for pick
up for only one fix in the past. Let me know if I need to generate a
formal PR.
Thanks in advace
next prev parent reply other threads:[~2023-10-17 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:22 [PATCH v2] riscv: dts: thead: set dma-noncoherent to soc bus Jisheng Zhang
2023-09-12 14:48 ` Guo Ren
2023-09-12 16:27 ` Conor Dooley
2023-09-13 15:15 ` Jisheng Zhang
2023-09-13 15:44 ` Conor Dooley
2023-09-20 8:36 ` Conor Dooley
2023-09-21 9:24 ` Jisheng Zhang
2023-09-21 10:08 ` Conor Dooley
2023-10-16 17:10 ` Drew Fustini
2023-10-17 16:09 ` Jisheng Zhang [this message]
2023-10-17 20:33 ` Arnd Bergmann
2023-11-12 0:55 ` patchwork-bot+linux-riscv
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=ZS6x18XEJXmB7FFL@xhacker \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.com \
--cc=guoren@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=wefu@redhat.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).