* Michael Opdenacker [150326 18:12]:
> This patch removes the use of the IRQF_DISABLED flag
> from drivers/bus/omap_l3_*
>
> It's a NOOP since 2.6.35 and it will be removed one day.
>
> Signed-off-by: Michael Opdenacker
> Acked-by: Santosh Shilimkar
Currently there are no other patches
On Mon, Mar 30, 2015 at 12:22:55PM +0100, Lee Jones wrote:
> On Mon, 23 Mar 2015, Charles Keepax wrote:
>
> > wm5102 applies a custom hardware boot sequence, for this the SYSCLK
> > needs to be enabled. This patch factors out the code that enables
> > SYSCLK for this sequence such that it can be
Use a #define constant instead of a hardcoded value
and use bool for an int used as a bool to reduce
structure size.
Miscellanea:
Neaten comments in structure definition.
Add #include of ieee80211.h
Signed-off-by: Joe Perches
---
net/mac80211/ieee80211_i.h | 7 ---
net/mac80211/rx.c
On Mon, Mar 30, 2015 at 09:26:07AM -0700, Darren Hart wrote:
> Fair point. This isn't a space I'm well versed in, but some standard means
> of doing this would be welcome.
I'm reading standard memes, time to get away from the keyboard for a
little while I suppose :-)
--
To unsubscribe from this
* Wang Long [150327 02:43]:
> If we set ramoops.mem_type=1 in command line, the current
> code can not change mem_type to 1, because it is assigned
> to 0 in function ramoops_register_dummy.
>
> This patch make it possible to change mem_type parameter
> in command line.
>
> Signed-off-by: Wang
On 3/29/15, 4:49 PM, "Michael Ellerman" wrote:
>On Fri, 2015-03-27 at 15:17 -0700, Darren Hart wrote:
>> Adapt the futextest Makefiles to use lib.mk macros for RUN_TESTS and
>> EMIT_TESTS. For now, we reuse the run.sh mechanism provided by
>> futextest. This doesn't provide the standard
On Mon, Mar 30, 2015 at 12:25:12PM -0400, Waiman Long wrote:
> I did it differently in my PV portion of the qspinlock patch. Instead of
> just waking up the CPU, the new lock holder will check if the new queue head
> has been halted. If so, it will set the slowpath flag for the halted queue
> head
On 3/29/15, 4:44 PM, "Michael Ellerman" wrote:
>On Fri, 2015-03-27 at 16:09 -0700, Darren Hart wrote:
>>
>> On 3/27/15 3:59 PM, Michael Ellerman wrote:
>> > On Fri, 2015-03-27 at 15:17 -0700, Darren Hart wrote:
>> >> Define the exit codes with KSFT_PASS and similar so tests can use
>>these
>>
On 03/25/2015 03:47 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Mar 16, 2015 at 02:16:13PM +0100, Peter Zijlstra wrote:
Hi Waiman,
As promised; here is the paravirt stuff I did during the trip to BOS last week.
All the !paravirt patches are more or less the same as before (the only real
change
On Mon, Mar 30, 2015 at 09:47:01PM +0530, Viresh Kumar wrote:
> And all I get it is 8256 bytes, with or without the change.
Duh, rounded up to cacheline boundary ;-)
Trades two 4 byte holes at the start for a bigger 'hole' at the end.
struct tvec_base {
spinlock_t lock;
On Mon, 2015-03-30 at 18:14 +0200, Michael Wang wrote:
> Hi, Doug
>
> Thanks for the comments :-)
>
> On 03/30/2015 05:56 PM, Doug Ledford wrote:
> > On Fri, 2015-03-27 at 16:40 +0100, Michael Wang wrote:
> >> We have so much places to check transport type and link layer type, it's
> >> now
>
On 03/30/2015 06:17 PM, Doug Ledford wrote:
> On Fri, 2015-03-27 at 16:42 +0100, Michael Wang wrote:
>> Introduce helper tech_iboe() to help us check if the port of an IB
>> device is using RoCE/IBoE technology.
> Just use rdma_transport_is_roce() instead.
Sounds good :-) will be in next version.
On 03/30/2015 06:13 PM, Doug Ledford wrote:
> On Fri, 2015-03-27 at 16:47 +0100, Michael Wang wrote:
>> Introduce helper has_iwarp() to help us check if an IB device
>> support IWARP protocol.
> This is a needless redirection. Just stick with the original
> rdma_transport_is_iwarp().
Agree, will
On 03/30/2015 06:11 PM, Doug Ledford wrote:
> On Fri, 2015-03-27 at 16:46 +0100, Michael Wang wrote:
>> Introduce helper has_mcast() and cap_mcast() to help us check if an
>> IB device or it's port support Multicast.
> This probably needs reworded or rethought. In truth, *all* rdma devices
> are
I wanted to ping the patch below again, since I haven't heard any
feedback.
I note that Rik van Riel's change posted this weekend offers similar
functionality for userspace. My change offers a convenient API
for, e.g., kernel drivers setting up default irq balancing.
On Fri, 2015-03-27 at 16:42 +0100, Michael Wang wrote:
> Introduce helper tech_iboe() to help us check if the port of an IB
> device is using RoCE/IBoE technology.
Just use rdma_transport_is_roce() instead.
> Cc: Jason Gunthorpe
> Cc: Doug Ledford
> Cc: Ira Weiny
> Cc: Sean Hefty
>
On Fri, 2015-03-27 at 16:46 +0100, Michael Wang wrote:
> Introduce helper has_sa() and cap_sa() to help us check if an IB device
> or it's port support Subnet Administrator.
There's no functional reason to have both rdma_transport_is_ib and
rdma_port_ll_is_ib, just use one. Then there is also no
Hello Tomasz,
Thanks a lot for your feedback.
On 03/30/2015 06:07 PM, Tomasz Figa wrote:
> Hi Javier,
>
> Please see my comments inline.
>
> 2015-03-31 0:53 GMT+09:00 Javier Martinez Canillas
> :
> [snip]
>> diff --git a/drivers/clk/samsung/clk-exynos5420.c
>>
On 30 March 2015 at 19:29, Peter Zijlstra wrote:
> Yeah, so that _should_ not trigger (obviously), and while I agree with
> the sentiment of sanity checks, I'm not sure its worth keeping that
> variable around just for that.
I read it as I can remove it then ? :)
> Anyway, while I'm looking at
Hi, Doug
Thanks for the comments :-)
On 03/30/2015 05:56 PM, Doug Ledford wrote:
> On Fri, 2015-03-27 at 16:40 +0100, Michael Wang wrote:
>> We have so much places to check transport type and link layer type, it's now
>> make sense to introduce some helpers in order to refine the lengthy code.
On Fri, 2015-03-27 at 16:47 +0100, Michael Wang wrote:
> Introduce helper has_iwarp() to help us check if an IB device
> support IWARP protocol.
This is a needless redirection. Just stick with the original
rdma_transport_is_iwarp().
> Cc: Jason Gunthorpe
> Cc: Doug Ledford
> Cc: Ira Weiny
>
On Fri, 2015-03-27 at 16:46 +0100, Michael Wang wrote:
> Introduce helper has_mcast() and cap_mcast() to help us check if an
> IB device or it's port support Multicast.
This probably needs reworded or rethought. In truth, *all* rdma devices
are multicast capable. *BUT*, IB/OPA devices require
Hi,
On Wed, Mar 18, 2015 at 12:17:28AM +, Chanwoo Choi wrote:
> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on
> Octal core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433 supports
> PSCI (Power State Coordination Interface) v0.1.
>
> This patch
Hello Tomasz,
On 03/30/2015 06:02 PM, Tomasz Figa wrote:
> Hi Javier,
>
> 2015-03-31 0:53 GMT+09:00 Javier Martinez Canillas
> :
>> The Samsung helpers functions to register clocks, add the clock instance
>> returned by the common clock framework to a lookup table that is used by
>> OF to lookup
Hi Javier,
Please see my comments inline.
2015-03-31 0:53 GMT+09:00 Javier Martinez Canillas
:
[snip]
> diff --git a/drivers/clk/samsung/clk-exynos5420.c
> b/drivers/clk/samsung/clk-exynos5420.c
> index 07d666cc6a29..2d39b629144a 100644
> --- a/drivers/clk/samsung/clk-exynos5420.c
> +++
2015-03-30 7:39 GMT-07:00 Stas Sergeev :
> 27.03.2015 20:15, Florian Fainelli пишет:
>> I think your concerns are valid, but I don't think there is going to be
>> any problem with the approach I suggested because there is a contract
>> that the fixed PHYs and regular PHYs need to
> Hello Florian.
On Thu, Mar 26, 2015 at 10:08 AM, Eric B Munson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/26/2015 07:56 AM, Davide Libenzi wrote:
>> On Wed, 25 Mar 2015, David Rientjes wrote:
>>
>>> I looked at this thread at http://marc.info/?t=14139250881
>>> since I didn't have it
Hi Javier,
2015-03-31 0:53 GMT+09:00 Javier Martinez Canillas
:
> The Samsung helpers functions to register clocks, add the clock instance
> returned by the common clock framework to a lookup table that is used by
> OF to lookup the clocks.
>
> But this table could also be useful to clock drivers
On Fri, 2015-03-27 at 16:40 +0100, Michael Wang wrote:
> We have so much places to check transport type and link layer type, it's now
> make sense to introduce some helpers in order to refine the lengthy code.
>
> This patch will introduce helpers:
> rdma_transport_is_ib()
>
Hello Chanwoo,
Thanks a lot for your feedback.
On 03/30/2015 04:04 AM, Chanwoo Choi wrote:
>
> I faced on the similiar issue. If some clock was disabled,
> Exynos SoC could not enter the suspend mode
>
> But, I think it is not prpper method to resolve this issue.
> about that that specific
The Samsung helpers functions to register clocks, add the clock instance
returned by the common clock framework to a lookup table that is used by
OF to lookup the clocks.
But this table could also be useful to clock drivers if they need to get
a clock instance since the helper functions don't
Commit ae43b3289186 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power
Management support v12") added pm support for the pl330 dma driver but
it makes the clock for the Exynos5420 MDMA0 DMA controller to be gated
during suspend and this clock needs to remain enabled in order to make
the system
Hello,
This series is a 3rd version of a RFC to fix Suspend-to-RAM on Exynos5420.
Abhilash Kesavan traced down to the MDMA0 DMA controller clock needed to
be enabled during suspend in order to make the system resume correctly.
I posted a RFC that grabbed the clock in the Exynos5420 specific
On 30 March 2015 at 08:04, Alexander Shishkin
wrote:
> Mathieu Poirier writes:
>
>> +static int stm_send(void *addr, const void *data, u32 size)
>> +{
>> + u32 len = size;
>> +
>> + if (((unsigned long)data & 0x1) && (size >= 1)) {
>> + writeb_relaxed(*(u8 *)data, addr);
>> +
Jaehoon,
On Sun, Mar 29, 2015 at 5:55 PM, Jaehoon Chung wrote:
> Dear Doug,
>
> I'm considering to control HLE error..So holding this patch.
> If this is absolutely necessary patch, let me know, plz.
>
> Best Regards,
> Jaehoon Chung
Sounds OK. I have certainly applied this locally and the
"Kirill A. Shutemov" writes:
> On Mon, Mar 30, 2015 at 08:38:08PM +0530, Aneesh Kumar K.V wrote:
>>
>>
>> +static void freeze_page(struct anon_vma *anon_vma, struct page *page)
>> > +{
>> > + struct anon_vma_chain *avc;
>> > + struct vm_area_struct *vma;
>> > + pgoff_t pgoff =
This change was detected with the help of coccinelle tool.
It performs the same function as kzalloc amd memcpy.
Signed-off-by: Chaitanya Dhere
---
drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
On Mon, 30 Mar 2015, Michal Hocko wrote:
> Why cannot we do something like refresh_cpu_vm_stats from the IRQ
> context? Especially the first zone stat part. The per-cpu pagesets is
> more costly and it would need a special treatment, alright. A simple
> way would be to splice the lists from the
"Kirill A. Shutemov" writes:
> Hello everybody,
>
> It's bug-fix update of my thp refcounting work.
>
> The goal of patchset is to make refcounting on THP pages cheaper with
> simpler semantics and allow the same THP compound page to be mapped with
> PMD and PTEs. This is required to get
On 3/30/15 2:01 AM, Jiri Olsa wrote:
On Sun, Mar 29, 2015 at 04:30:01PM -0600, David Ahern wrote:
SNIP
+ fd = open(filename, O_RDONLY);
+ if (fd < 0) {
pr_debug("couldn't open %s\n", filename);
return 0;
}
- while (!comm[0] || (tgid <
So this driver builds as a module.
Signed-off-by: Tomeu Vizoso
---
v2: * Remove governor if driver registration fails
---
drivers/devfreq/tegra-devfreq.c | 37 ++---
1 file changed, 30 insertions(+), 7 deletions(-)
diff --git
Hi
This is a follow-up for:
http://lkml.kernel.org/r/<201412181916.18051.s@gmx.de>
http://lkml.kernel.org/r/<201412302211.40801.s@gmx.de>
On 2014-12-30, Stefan Lippers-Hollmann wrote:
> On Thursday 18 December 2014, Stefan Lippers-Hollmann wrote:
> > Occassionally, but
Em Mon, Mar 30, 2015 at 09:23:21AM -0600, David Ahern escreveu:
> On 3/30/15 2:04 AM, Jiri Olsa wrote:
> >On Sun, Mar 29, 2015 at 04:30:02PM -0600, David Ahern wrote:
> >
> >SNIP
> >
> >>-static pid_t perf_event__synthesize_comm(struct perf_tool *tool,
> >>-
On Mon, Mar 30, 2015 at 08:38:08PM +0530, Aneesh Kumar K.V wrote:
>
>
> +static void freeze_page(struct anon_vma *anon_vma, struct page *page)
> > +{
> > + struct anon_vma_chain *avc;
> > + struct vm_area_struct *vma;
> > + pgoff_t pgoff = page->index << (PAGE_CACHE_SHIFT -
On Mon, Mar 30, 2015 at 02:29:09PM +0100, Vincent Guittot wrote:
> On 30 March 2015 at 14:24, Peter Zijlstra wrote:
> > On Mon, Mar 30, 2015 at 01:03:03PM +0100, Morten Rasmussen wrote:
> >> On Mon, Mar 30, 2015 at 12:06:32PM +0100, Peter Zijlstra wrote:
> >> > On Fri, Mar 27, 2015 at 05:56:51PM
On 3/30/15 2:04 AM, Jiri Olsa wrote:
On Sun, Mar 29, 2015 at 04:30:02PM -0600, David Ahern wrote:
SNIP
-static pid_t perf_event__synthesize_comm(struct perf_tool *tool,
-union perf_event *event, pid_t pid,
-
On Mon, Mar 30, 2015 at 07:49:43PM +0530, Aneesh Kumar K.V wrote:
> "Kirill A. Shutemov" writes:
>
> > Currently, we rely on compound_lock() to get page counts stable on
> > splitting page refcounting. To get it work we also take the lock on
> > get_page() and put_page() which is hot path.
> >
>
gt; The ARM VDSO stuff will just have to wait for 4.2 instead.
>>>
>>> If that works for you.
>>
>> FWIW, Stephen's merge fix is correct and I have run my vdso tests
>> without problems on OMAP5 with next-20150330.
>
> Hopefully, I can pull the tip stuff b
Use a define instead of raw number as a ID for "rtc_src" clock.
Signed-off-by: Krzysztof Kozlowski
---
Patch depends on new file "dt-bindings/clock/samsung,s2mps11.h" from:
http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg43136.html
---
arch/arm/boot/dts/exynos3250-rinato.dts
On Mon, Mar 30, 2015 at 07:40:29PM +0530, Aneesh Kumar K.V wrote:
> "Kirill A. Shutemov" writes:
>
> > We're going to use migration entries instead of compound_lock() to
> > stabilize page refcounts. Setup and remove migration entries require
> > page to be locked.
> >
> > Some of
Mark "samsung,exynos3250-rtc" compatible as deprecated because it
duplicates the "samsung,s3c6410-rtc". Use "samsung,s3c6410-rtc" on
Exynos3250 and Exynos4415 boards.
Signed-off-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/rtc/s3c-rtc.txt | 3 ++-
There are now no differences between RTC on Exynos3250 and S3C6410.
Merge everything into one so duplicated code could be removed.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-s3c.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git
Hi,
Now the s3c6410-rtc is exactly the same as exynos3250-rtc. Mark the
second one as deprecated and switch to one binding.
Patches are independent.
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
drivers/rtc/rtc-s3c.c: Integrate Exynos3250 into S3C6410
ARM: dts: s3c-rtc: Use s3c6410-rtc
The example is wrong in that the phys property should take a
phandle to the phy port.
Also with the changing over to generic PHY type constants we also
update that as well.
Signed-off-by: Peter Griffin
Acked-by: Rob Herring
Acked-by: Lee Jones
---
Now there are generic phy type constants declared in phy.h, migrate over to
using them rather than defining our own. This change has been done as one
atomic commit to be bisectable.
Note: The values of the defines are the same, so there is no ABI breakage
with this patch.
Signed-off-by: Peter
Ths picophyreset is incorrectly defined, which stops the usb2 phy being
taken out of reset.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/boot/dts/stih407-family.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
There is a subtle typo phys-names should be phy-names. Using the
current example means you don't have working usb (as you fail to
obtain the phys). Also update the example to use the generic phy
type constants which are now used for miphy28.
Additionaly also remove the unnecessary new line in the
This patch adds the phy-miphy28lp.c phy driver found on STMicroelectronics
stih407 family SoC's into the STI arch section of the maintainers file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
Hi,
This series primarily adds the dwc3 DT node which activates the usb3 controller
on
the stih407-b2120 and stih410-b2120 platforms.
As part of getting this working I noticed some various errors with the DT
documentation examples for how we reference the PHYs which I've also fixed.
Whilst
Now that both usb2 and usb3 phy drivers, and also the ST dwc3 glue code
are all present upstream, we can add the dwc3 DT node and have a working
usb3 controller on stih407-b2120 and stih410-b2020.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
arch/arm/boot/dts/stih407-family.dtsi | 25
On Mon, Mar 30, 2015 at 05:08:18PM +0200, Michal Hocko wrote:
> On Sat 28-03-15 10:53:22, Peter Zijlstra wrote:
> [...]
> > Alternatively the thing hocko suggests is an utter fail too. You cannot
> > stuff that into hardirq context, that's insane.
>
> I guess you are referring to
>
Em Mon, Mar 30, 2015 at 11:58:05AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Mar 30, 2015 at 09:48:52PM +0900, Namhyung Kim escreveu:
> > But this makes every sample processing grabs and releases the lock so
> > might cause high overhead. It can be a problem if such processing is
> >
l you really
> > need to merge is tip timers/core branch (which I am sure the tip guys
> > can tell you if it is stable enough) which is about 28 commits ...
> >
> >> The ARM VDSO stuff will just have to wait for 4.2 instead.
> >
> > If that works for yo
On Mon, Mar 30, 2015 at 02:54:38PM +0200, Tomeu Vizoso wrote:
[...]
> +static int __init tegra_devfreq_init(void)
> +{
> + int ret = 0;
> +
> + ret = devfreq_add_governor(_devfreq_governor);
> + if (ret) {
> + pr_err("%s: failed to add governor: %d\n", __func__, ret);
> +
On Sat 28-03-15 10:53:22, Peter Zijlstra wrote:
[...]
> Alternatively the thing hocko suggests is an utter fail too. You cannot
> stuff that into hardirq context, that's insane.
I guess you are referring to
http://article.gmane.org/gmane.linux.kernel.mm/127569, right?
Why cannot we do something
On 03/27/2015 06:29 PM, Jason Gunthorpe wrote:
> On Fri, Mar 27, 2015 at 01:16:31PM -0400, ira.weiny wrote:
>> [snip]
> http://www.spinics.net/lists/linux-rdma/msg22565.html
>
> ''Unlike IB, the iWARP protocol only allows 1 target/sink SGE in an
> rdma read''
>
> It is one of those annoying verbs
On 3/30/2015 4:43 AM, Borislav Petkov wrote:
On Mon, Mar 30, 2015 at 11:26:34AM +0200, Geert Uytterhoeven wrote:
On Sun, Mar 29, 2015 at 3:56 PM, Borislav Petkov wrote:
From: Borislav Petkov
Let's make it official - I've been doing this for a while now anyway.
Signed-off-by: Borislav
+static void freeze_page(struct anon_vma *anon_vma, struct page *page)
> +{
> + struct anon_vma_chain *avc;
> + struct vm_area_struct *vma;
> + pgoff_t pgoff = page->index << (PAGE_CACHE_SHIFT - PAGE_SHIFT);
So this get called only with head page, We also do
On Mon, 30 Mar 2015, Andy Lutomirski wrote:
> > Would this suffice? It puts the CAP_SETPCAP limitation back to how it
> > was in my earlier patch.
> I really don't like that variant. CAP_SETPCAP is dangerous and so
> absurdly powerful that people really shouldn't hand it out.
According to
On 03/30/2015 05:51 AM, fangwei wrote:
Don't assign ->rq_timeout twice.
Thanks, applied.
--
Jens Axboe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Em Mon, Mar 30, 2015 at 09:48:52PM +0900, Namhyung Kim escreveu:
> Hi Jiri,
>
> On Mon, Mar 30, 2015 at 01:49:07PM +0200, Jiri Olsa wrote:
> > On Mon, Mar 30, 2015 at 01:21:08PM +0200, Jiri Olsa wrote:
> > > On Mon, Mar 30, 2015 at 12:22:20PM +0200, Jiri Olsa wrote:
> > > > On Mon, Mar 30, 2015
enough) which is about 28 commits ...
>
>> The ARM VDSO stuff will just have to wait for 4.2 instead.
>
> If that works for you.
FWIW, Stephen's merge fix is correct and I have run my vdso tests
without problems on OMAP5 with next-20150330.
--
To unsubscribe from this list:
On Thu 26-03-15 12:50:20, David Rientjes wrote:
[...]
> android, lmk: avoid setting TIF_MEMDIE if process has already exited
>
> TIF_MEMDIE should not be set on a process if it does not have a valid
> ->mm, and this is protected by task_lock().
>
> If TIF_MEMDIE gets set after the mm has
On Mon, Mar 30, 2015 at 02:23:47PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > Signed-off-by: Dave Airlie
> > > Signed-off-by: Gerd Hoffmann
> >
> > Standard request from my side for new drm drivers (especially if they're
> > this simple): Can you please update the drivers to latest drm
On Mon, 2015-03-30 at 07:03 -0600, David Ahern wrote:
> On 3/29/15 9:08 PM, Mike Galbraith wrote:
> >
> > Oh, you can add /proc/sys/kernel/sched_domain diddling to the hotplug
> > todo... which will either create read /sys, poke modify buttons over
> > yonder in /proc situation, or have to
On Mon, Mar 30, 2015 at 7:30 AM, Andy Lutomirski wrote:
> On Mon, Mar 30, 2015 at 7:27 AM, Denys Vlasenko wrote:
>> On 03/26/2015 07:45 PM, Andy Lutomirski wrote:
>>> On Thu, Mar 26, 2015 at 5:42 AM, Denys Vlasenko wrote:
This change makes the check exact (no more false positives
on
Needed in several Chromebook models such as the Tegra-based ones.
Signed-off-by: Tomeu Vizoso
---
arch/arm/configs/multi_v7_defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 5b4d1c8..7ffa4aa 100644
Signed-off-by: Tomeu Vizoso
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 7ffa4aa..17e89b0 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++
Signed-off-by: Michael Mueller
---
linux-headers/asm-s390/kvm.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/linux-headers/asm-s390/kvm.h b/linux-headers/asm-s390/kvm.h
index c5a93eb..bfe6925 100644
--- a/linux-headers/asm-s390/kvm.h
+++
Needed in several Chromebook models such as the Tegra-based ones.
Signed-off-by: Tomeu Vizoso
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index 8e174ea..5b4d1c8 100644
---
This brings the DevFreq framework in and builds the ACTMON driver that
on Tegra124 will scale the external memory clock based on current load.
Signed-off-by: Tomeu Vizoso
---
arch/arm/configs/multi_v7_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git
This patch updates the binding information to reflect the
extra dt options which are now supported by the sdhci-st.c
driver which enable support for stih407 family silicon.
STiH410 SoC and later support UHS modes for eMMC, so the
driver now makes use of these common bindings. Examples
are
Add dt nodes to enable sdhci / eMMC for stih418-b2199 board.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih418-b2199.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/stih418-b2199.dts
b/arch/arm/boot/dts/stih418-b2199.dts
index 926235c..a2fdada
The nodes have been split to allow as much commonality as possible.
The stih407 has a silicon bug with eMMC UHS modes (with top regs)
and as such doesn't have any of the uhs dt properties.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-family.dtsi | 30 ++
To allow UHS modes to work properly we need to provide the st specific
set_uhs_signaling callback function. This function differs from the
generic sdhci_set_uhs_signaling callback in that we need to configure
the correct delay depending on the UHS mode, and also set the V18_EN
bit.
Signed-off-by:
Due to the tight timing constraints in some UHS modes, it is required to have
some delay management in the design. Two types of delay management are supported
in the HW: -
1) Static delay management
2) Dynamic delay management
NB: The delay management is only there when eMMC interface is
STiH407 family SoC's can have a reset signal for the controller which needs to
be managed. Also the eMMC controller has some additional 'top' memory mapped
registers which are used to manage the dynamic and static delay required for
UHS modes. This patch adds support for creating the mapping,
Hi,
This series adds sd/emmc support to the sdhci-st.c driver for stih407
family silicon. The changes mainly involve configuring some extra glue
registers in the flashSS which configure the Arasan controller.
This series also adds support for UHS modes for eMMC. To allow
UHS HS200/SD104 modes to
Some additional quirks need to be enabled now we support UHS
modes. This avoids some spurious warnings like
"Got data interrupt 0x0002 even though no data operation was in progress"
Testing on stih410-b2120 board achieves the following speeds
with HS200 eMMC card.
max-frequency = 200Mhz
The stih407 family SoC's have additional glue registers in the flashSS which
are used to configure the Arasan controller.
This patch adds macros for the register offsets and bitfields which will be
used by subsequent patches to support stih407 family SoC's.
Signed-off-by: Peter Griffin
STiH407 family SoC's have glue registers in the flashSS subsystem which
are used to configure the Arasan HC. This patch configures these glue
registers according to what has been specified in the DT.
Signed-off-by: Peter Griffin
Signed-off-by: Giuseppe Cavallaro
Acked-by: Maxime Coquelin
---
27.03.2015 20:15, Florian Fainelli пишет:
> I think your concerns are valid, but I don't think there is going to be
> any problem with the approach I suggested because there is a contract
> that the fixed PHYs and regular PHYs need to
Hello Florian.
As promised, today I tried to resurrect my
This patch implements the static part of the s390 cpu class definitions.
It defines s390 cpu models by means of virtual cpu ids (enum) which contain
information on the cpu generation, the machine class, the GA number and
the machine type. The cpu id is used to instantiate a cpu class per cpu
The patch introduces S390 CPU facility bit numbers and names
as well as the architectural facility size limit in bytes.
Signed-off-by: Michael Mueller
---
target-s390x/cpu-facilities.h | 86 +++
1 file changed, 86 insertions(+)
create mode 100644
The patch implements routines to set and retrieve processor configuration
data and to retrieve machine configuration data. The machine related data
is used together with the cpu model facility lists to determine the list of
supported cpu models of this host. The above mentioned routines have QEMU
This patch set in combination with its kernel kvm patch set proposes an
implementation of S390 cpu models. The origin of this item is to provide
a means for management interfaces like libvirt to draw decisions if life
guest migration to a target hypervisor is reasonable.
A migration constraint is
On 30 March 2015 at 08:19, Alexander Shishkin
wrote:
> Mathieu Poirier writes:
>
>> Hey Alex,
>
> Hi Mathieu,
>
>> Have a look at the following patch and see if you agree with my approach.
>> If so
>> simply add the code to a third version.
>
> Greg's comment about the two levels of ioctls got
This patch implements the infrastructure to dynamically add cpu
model aliases.
Signed-off-by: Michael Mueller
Reviewed-by: Cornelia Huck
---
target-s390x/cpu-models.c | 89 +++
target-s390x/cpu-models.h | 11 ++
target-s390x/cpu.c| 1 +
This patch provides routines to dynamically update the previously defined
S390 cpu classes in the current host context. The main function performing
this process is s390_setup_cpu_classes(). It takes the current host context
and a facility list mask as parameter to setup the classes accordingly.
On Mon, 30 Mar 2015, Steven Rostedt wrote:
> Hmm, I didn't realize there was an "and" version. I'm guessing this
> would bring down the instruction count even more?
Yes two segment prefixed instructions and a decrement.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
501 - 600 of 1870 matches
Mail list logo
