From: Nishanth Menon <nm@ti.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
"santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>,
Russell King <linux@arm.linux.org.uk>,
Santosh <ssantosh@kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH V2 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support.\
Date: Sat, 3 Jan 2015 09:39:30 -0600 [thread overview]
Message-ID: <20150103153930.GA26181@kahuna> (raw)
In-Reply-To: <CA+Ln22E0_R1cXXgF_L8kdz+cTmAkhykTtN04=q6JXNsUsFv9Eg@mail.gmail.com>
On 15:42-20150103, Tomasz Figa wrote:
> Indeed, as I figured out in the original thread about this issue,
> additional patch fixing code unaffected by my series (besides changing
> the condition which triggers calling it) is necessary. Namely, the
> affected 4 registers need to be written using the write_sec wrapper,
> instead of using writel*() directly.
>
Agreed. Would you like to post a patch (independent) of your series to address
this - sounds like a fix that should go in independent of your original
series.
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support.\
Date: Sat, 3 Jan 2015 09:39:30 -0600 [thread overview]
Message-ID: <20150103153930.GA26181@kahuna> (raw)
In-Reply-To: <CA+Ln22E0_R1cXXgF_L8kdz+cTmAkhykTtN04=q6JXNsUsFv9Eg@mail.gmail.com>
On 15:42-20150103, Tomasz Figa wrote:
> Indeed, as I figured out in the original thread about this issue,
> additional patch fixing code unaffected by my series (besides changing
> the condition which triggers calling it) is necessary. Namely, the
> affected 4 registers need to be written using the write_sec wrapper,
> instead of using writel*() directly.
>
Agreed. Would you like to post a patch (independent) of your series to address
this - sounds like a fix that should go in independent of your original
series.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-01-03 15:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 17:43 [PATCH V2 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-02 17:43 ` [PATCH V2 1/2] ARM: l2c: OMAP4/AM437x: Introduce support for cache latency programming Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-02 17:43 ` [PATCH V2 2/2] ARM: l2c: AM437x: Introduce support for cache filter programming Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-02 17:43 ` Nishanth Menon
2015-01-03 6:40 ` Tomasz Figa
2015-01-03 6:40 ` Tomasz Figa
2015-01-03 15:34 ` Nishanth Menon
2015-01-03 15:34 ` Nishanth Menon
2015-01-03 16:16 ` Tomasz Figa
2015-01-03 16:16 ` Tomasz Figa
2015-01-03 16:45 ` Nishanth Menon
2015-01-03 16:45 ` Nishanth Menon
2015-01-04 7:47 ` Tomasz Figa
2015-01-04 7:47 ` Tomasz Figa
2015-01-02 18:46 ` [PATCH V2 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support santosh.shilimkar
2015-01-02 18:46 ` santosh.shilimkar at oracle.com
2015-01-02 19:47 ` Nishanth Menon
2015-01-02 19:47 ` Nishanth Menon
2015-01-02 19:47 ` Nishanth Menon
2015-01-03 0:23 ` Tony Lindgren
2015-01-03 0:23 ` Tony Lindgren
2015-01-03 6:42 ` Tomasz Figa
2015-01-03 6:42 ` Tomasz Figa
2015-01-03 15:39 ` Nishanth Menon [this message]
2015-01-03 15:39 ` [PATCH V2 0/2] ARM: l2c: OMAP4/AM437x: Additional register programming support.\ Nishanth Menon
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=20150103153930.GA26181@kahuna \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=nsekhar@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--cc=tomasz.figa@gmail.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.