On Fri, 31 Jul 2015 14:14:28 +0800 Chen-Yu Tsai wrote:
> On Fri, Jul 31, 2015 at 1:51 PM, Bruno Prémont wrote:
> > Hi ChenYu,
> >
> > On Fri, 31 Jul 2015 13:31:53 +0800 Chen-Yu Tsai wrote:
> >> Hi Hans,
> >>
> >> On Wed, Jun 10, 2015 at 5:37 AM, Hans de Goede wrote:
> >> > Add a node representing t
On Fri, Jul 31, 2015 at 1:51 PM, Bruno Prémont
wrote:
> Hi ChenYu,
>
> On Fri, 31 Jul 2015 13:31:53 +0800 Chen-Yu Tsai wrote:
>> Hi Hans,
>>
>> On Wed, Jun 10, 2015 at 5:37 AM, Hans de Goede wrote:
>> > Add a node representing the usb power supply part of the axp209 pmic, note
>> > that the usb p
Hi ChenYu,
On Fri, 31 Jul 2015 13:31:53 +0800 Chen-Yu Tsai wrote:
> Hi Hans,
>
> On Wed, Jun 10, 2015 at 5:37 AM, Hans de Goede wrote:
> > Add a node representing the usb power supply part of the axp209 pmic, note
> > that the usb power supply and the (to be added later) ac power supply will
> >
Hi.
2015-07-30 10:30 GMT+09:00 Masahiro Yamada :
> Hi,
>
>
> 2015-07-30 0:23 GMT+09:00 Rob Herring :
>> On Wed, Jul 29, 2015 at 8:22 AM, Ian Campbell
>> wrote:
>>> On Wed, 2015-07-29 at 20:07 +0900, Masahiro Yamada wrote:
Hi Ian,
2015-07-27 19:35 GMT+09:00 Ian Campbell :
Hi Hans,
On Wed, Jun 10, 2015 at 5:37 AM, Hans de Goede wrote:
> Add a node representing the usb power supply part of the axp209 pmic, note
> that the usb power supply and the (to be added later) ac power supply will
> each have their own child-node, so that they can be separately specified
> as
On Thu, Jul 30, 2015 at 06:25:06PM +0200, Jan Lübbe wrote:
> On Mi, 2015-07-29 at 17:03 +0800, Haibo Chen wrote:
> > tuning-step is the delay cell steps in tuning procedure. The default
> > value of tuning-step is 1. For imx6 series usdhc, tuning procedure can
> > be passed when the tuning-step val
On Wed, Jul 29, 2015 at 5:15 PM, Marc Zyngier wrote:
>
> On 29/07/15 09:52, Ley Foon Tan wrote:
> > On Wed, Jul 29, 2015 at 1:58 AM, Marc Zyngier wrote:
> >> Hi Ley,
> >>
> >> On 28/07/15 11:45, Ley Foon Tan wrote:
> >>> This patch adds Altera PCIe MSI driver. This soft IP supports configurable
>
On Wed, 2015-07-22 at 16:14 +0800, Yingjoe Chen wrote:
> Spurious mtk timer interrupt is noticed at boot and cause kernel
> crash. It seems if GPT is enabled, it will latch irq status even
> when its IRQ is disabled. When irq is enabled afterward, we see
> spurious interrupt.
> Change init flow to
On Thu, 2015-07-30 at 21:29 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Change in v4:
> > 1. fix Mark Brown review comment.
>
> You should say what you actually fixed/changed, not just that you
> changed something. Also the individual patches should
Hi Jonas,
On Thu, 2015-07-30 at 21:27 +0200, Jonas Gorski wrote:
> Hi,
>
> On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> > Signed-off-by: Leilk Liu
> > ---
> > .../devicetree/bindings/spi/spi-mt65xx.txt | 38
> > ++
> > 1 file changed, 38 insertions(+)
> > c
Hi Sergei,
On Fri, Jul 31, 2015 at 4:59 AM, Sergei Shtylyov
wrote:
> The "compatible" property text contradicts even the example given in the MMCIF
> binding document itself; moreover, the Renesas MMCIF driver only matches on
> the generic "compatible" string, and doesn't look for at SoC specif
Dmitry,
Thank your very much.
Thanks,
Dudley
> -Original Message-
> From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
> Sent: 2015?7?31? 2:33
> To: Dudley Du
> Cc: mark.rutl...@arm.com; robh...@kernel.org; ble...@google.com;
> jmmah...@gmail.com; devicetree@vger.kernel.org; linux-
Signed-off-by: Moritz Fischer
---
arch/arm/boot/dts/zynq-7000.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/zynq-7000.dtsi b/arch/arm/boot/dts/zynq-7000.dtsi
index 0691508..6bebf02 100644
--- a/arch/arm/boot/dts/zynq-7000.dtsi
+++ b/arch/arm/boot/dts/zynq-7000
Signed-off-by: Moritz Fischer
---
.../devicetree/bindings/reset/zynq-reset.txt | 68 ++
1 file changed, 68 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset.txt
diff --git a/Documentation/devicetree/bindings/reset/zynq-reset.txt
b/Doc
Hi all,
I made another RFC addressing most of the feedback that I got so far.
I haven't completly given up on Sören's idea of getting rid of having
some sort of protection against people using wrong bits by accident,
but haven't come up with a clean way to do so yet (especially when looking at
th
This adds a reset controller driver to control the Xilinx Zynq
AP-SoC's various resets.
Signed-off-by: Moritz Fischer
---
drivers/reset/Makefile | 1 +
drivers/reset/reset-zynq.c | 155 +
2 files changed, 156 insertions(+)
create mode 100644 dri
Signed-off-by: Moritz Fischer
---
arch/arm/mach-zynq/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-zynq/Kconfig b/arch/arm/mach-zynq/Kconfig
index 78e5e00..77d7df7 100644
--- a/arch/arm/mach-zynq/Kconfig
+++ b/arch/arm/mach-zynq/Kconfig
@@ -1,5 +1,6 @@
config ARCH_ZYN
On 29 July 2015 at 15:47, Ezequiel Garcia wrote:
> +devicetree guys
>
> On 28 July 2015 at 20:22, Joachim Eastwood wrote:
>> On 29 July 2015 at 00:45, Ezequiel Garcia
>> wrote:
>>> On 28 July 2015 at 19:37, Joachim Eastwood wrote:
On 27 July 2015 at 06:45, Ariel D'Alessandro
wrot
On Tue, Jul 28, 2015 at 12:44 PM, Lorenzo Pieralisi
wrote:
> [CC'ing RMK]
>
> On Tue, Jul 28, 2015 at 08:17:18AM +0100, Zhou Wang wrote:
>> On 2015/7/25 11:21, Zhou Wang wrote:
>> > From: Gabriele Paoloni
>> >
>> > This patch is needed in order to unify the PCIe designware framework for
>> > ARM
On Thu, Jul 30, 2015 at 5:13 PM, Stephen Boyd wrote:
> On 07/22/2015 10:08 PM, Krzysztof Kozlowski wrote:
>>
>> 2015-07-21 20:07 GMT+09:00 Vaibhav Hiremath :
>>>
>>> This patch updates the binding documentation for optional
>>> clocks node and related information for buffered 32KHz clock.
>>>
>>>
On 07/22/2015 10:08 PM, Krzysztof Kozlowski wrote:
2015-07-21 20:07 GMT+09:00 Vaibhav Hiremath :
This patch updates the binding documentation for optional
clocks node and related information for buffered 32KHz clock.
Signed-off-by: Vaibhav Hiremath
---
Documentation/devicetree/bindings/mfd/8
Define the SILK board dependent part of the MMCIF device node (the board has
eMMC chip) along with the necessary voltage regulator (note that the Vcc/Vccq
regulator is dummy -- it's required by the MMCIF driver but doesn't actually
exist on the board).
Based on the original patch by Vladimir Bari
Define the generic R8A7794 part of the MMCIF0 device node.
Based on the orginal patch by Shinobu Uehara .
Signed-off-by: Sergei Shtylyov
---
Changes in version 2:
- updated the patch due to the SDHI patch being accepted first;
- refreshed the patch.
arch/arm/boot/dts/r8a7794.dtsi | 11
Hello.
Here's the set of 2 patches against Simon Horman's 'renesas.git' repo,
'renesas-devel-20150730-v4.2-rc4' tag. Here we add the eMMC device tree support
for the R8A7794-based SILK board.
[1/2] ARM: shmobile: r8a7794: add MMCIF DT support
[2/2] ARM: shmob
Hi Mike,
I encountered some trouble while I tried to implement code fitting to DTS
that you proposed. SIM_CLKDIVx are SIM device registers, not MCG.
Therefore, in MCG device code I won't be able to figure out clock rate
for outputed clocks unles I try to access SIM registers from MCG driver -
Hello,
while hacking on the gpio driver I found yet another ambiguity:
On Tue, Jul 28, 2015 at 10:33:48PM +0200, Uwe Kleine-König wrote:
> - - level: Low or high level starts counting WDT timeout,
> -the opposite level disables the WDT. Active level is determined
> -by the GPIO flags.
Th
Renesas R8A7793 and R8A7793 SoC also have the MMCIF controller...
Signed-off-by: Sergei Shtylyov
---
The patch is against Ulf Hansson's 'mmc.git' repo's 'next' branch plus the
patch I posted earlier today...
Documentation/devicetree/bindings/mmc/renesas,mmcif.txt |2 ++
1 file changed, 2
On Thu, Jul 30, 2015 at 12:34 PM, Gabriele Paoloni
wrote:
>> -Original Message-
>> From: Bjorn Helgaas [mailto:bhelg...@google.com]
>> Sent: 30 July 2015 18:15
>> On Thu, Jul 30, 2015 at 04:50:55PM +, Gabriele Paoloni wrote:
>> > > -Original Message-
>> > > From: linux-pci-ow..
Hello.
On 07/30/2015 10:59 PM, Sergei Shtylyov wrote:
The "compatible" property text contradicts even the example given in the MMCIF
binding document itself; moreover, the Renesas MMCIF driver only matches on
the generic "compatible" string, and doesn't look for at SoC specific strings
"
On Thu, 2015-07-30 at 07:47 +0300, Igal.Liberman wrote:
> From: Igal Liberman
>
> Describe the PHY topology for all configurations supported by each board
>
> Based on prior work by Andy Fleming
>
> Signed-off-by: Igal Liberman
> Signed-off-by: Shruti Kanetkar
> Signed-off-by: Emil Medve
S
On Thu, 2015-07-30 at 07:32 +0300, Igal.Liberman wrote:
> +fman0: fman@40{
> + #address-cells = <1>;
> + #size-cells = <1>;
> + cell-index = <0>;
> + compatible = "fsl,fman";
> + ranges = <0 0x40 0x10>;
> + reg = <0x40 0x10>;
> + interrupts = <96 2 0
On Thu, 2015-07-30 at 07:33 +0300, Igal.Liberman wrote:
> @@ -307,4 +307,117 @@
> reg = <0xe 0x1000>;
> fsl,has-rstcr;
> };
> +
> + fman@10{
> + #address-cells = <1>;
> + #size-cells = <1>;
> + cell-index = <0>;
> +
Hi Stefan,
Le Thu, 30 Jul 2015 19:00:38 +0200, Stefan Agner a
écrit :
> Hi Albert,
>
> On 2015-07-30 18:13, Albert ARIBAUD wrote:
> > Hi Stefan,
> >
> > Le Mon, 27 Jul 2015 18:42:41 +0200, Stefan Agner a
> > écrit :
> >
> >> This driver supports Freescale NFC (NAND flash controller) found on
Am Donnerstag, 30. Juli 2015, 12:42:44 schrieb Stephen Boyd:
> On 07/30/2015 11:04 AM, Heiko Stübner wrote:
> > Am Donnerstag, 30. Juli 2015, 10:36:43 schrieb Stephen Boyd:
> >> Is it being used in DT right now and causing regressions on
> >> v4.2-rcX? Sorry, I'm trying to understand why this patch
The "compatible" property text contradicts even the example given in the MMCIF
binding document itself; moreover, the Renesas MMCIF driver only matches on
the generic "compatible" string, and doesn't look for at SoC specific strings
currently at all. Thus describe "renesas,sh-mmcif" string as man
On 07/30/2015 11:04 AM, Heiko Stübner wrote:
Am Donnerstag, 30. Juli 2015, 10:36:43 schrieb Stephen Boyd:
Is it being used in DT right now and causing regressions on
v4.2-rcX? Sorry, I'm trying to understand why this patch matters
for the 4.2 release.
it's not been used in an actual devicetree
Hi,
On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> Change in v4:
> 1. fix Mark Brown review comment.
You should say what you actually fixed/changed, not just that you
changed something. Also the individual patches should contain
changelogs as well (under the tear-off line (--), so one knows
Hi,
On Wed, Jul 29, 2015 at 1:04 PM, Leilk Liu wrote:
> Signed-off-by: Leilk Liu
> ---
> .../devicetree/bindings/spi/spi-mt65xx.txt | 38
> ++
> 1 file changed, 38 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/spi-mt65xx.txt
>
> diff --gi
Hi,
Sorry for the corss-talk on my previous reply.
> I am trying to instantiate generic PM domains for different CPU clusters
> commonly. Individual platform code may have different actions for
> powering down/up the CPU domain. It could be different set of bucks that
> they need to talk to or bu
On Fri, Jul 24, 2015 at 01:05:58PM +0800, Dudley Du wrote:
> Add of_match_device mechanism support for Cypress trackpad device, and
> add the sample description document on how to adding the trackpad device node
> in the device tree.
>
> Signed-off-by: Dudley Du
Applied, thank you.
> ---
> ...
Am Donnerstag, 30. Juli 2015, 10:36:43 schrieb Stephen Boyd:
> On 07/29, James Liao wrote:
> > Hi Stephen,
> >
> > Could you help to apply this patch into 4.2?
> >
> >
> > Best regards,
> >
> > James
> >
> > On Wed, 2015-07-29 at 09:05 +0200, Heiko Stübner wrote:
> > > Am Mittwoch, 29. Juli 20
On Fri, Jul 24, 2015 at 01:05:59PM +0800, Dudley Du wrote:
> Avoid the driver generate warning message when the cyapa driver working
> with the old Gen5 trackpad device which does not support the proximity
> function.
> Those old Gen5 trackpad device all have the platform version less than 2.
>
>
On Fri, Jul 24, 2015 at 01:05:57PM +0800, Dudley Du wrote:
> Add power management regulator vcc support.
> It's described to be supported in the cypress,cyapa.txt document.
>
> Signed-off-by: Dudley Du
It looks like we were missing linux/regulator/consumer.h include, I
added it and applied.
Tha
From: Courtney Cavin
Signed-off-by: Courtney Cavin
Signed-off-by: Bjorn Andersson
---
Changes since v1:
- Corrected authorship
arch/arm/boot/dts/qcom-pm8941.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-pm8941.dtsi
b/arch/arm/boot/dts
From: Courtney Cavin
Add the Qualcomm Switch-Mode Battery Charger and Boost device tree
binding.
Signed-off-by: Courtney Cavin
Signed-off-by: Bjorn Andersson
---
Changes since v1:
- Corrected authorship
.../devicetree/bindings/power_supply/qcom_smbb.txt | 131 +
1 file c
This series adds bindings and a device driver for the Qualcomm Switch-Mode
Battery Charger and Boost block found in pm8941.
Changes since v1:
- Corrected authorship of the patches
- Gave dt properties qcom vendor prefix
- Updated names of dt properties
- Dropped MODULE_ALIAS
Courtney Cavin (4):
On 07/29, James Liao wrote:
> Hi Stephen,
>
> Could you help to apply this patch into 4.2?
>
>
> Best regards,
>
> James
>
> On Wed, 2015-07-29 at 09:05 +0200, Heiko Stübner wrote:
> > Am Mittwoch, 29. Juli 2015, 14:52:25 schrieb James Liao:
> > > The dpi_ck clock can be removed because it not
> -Original Message-
> From: Bjorn Helgaas [mailto:bhelg...@google.com]
> Sent: 30 July 2015 18:15
> To: Gabriele Paoloni
> Cc: Rob Herring; a...@arndb.de; lorenzo.pieral...@arm.com; Wangzhou (B);
> robh...@kernel.org; james.mo...@arm.com; liviu.du...@arm.com; linux-
> p...@vger.kernel.or
Enable the otg/drc usb controller on the Wexler TAB7200 tablet.
Signed-off-by: Aleksei Mamlin
---
arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts | 32 ++
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/sun7i-a20-wexler-tab7200.dts
b/arch/arm/boot/dts/sun
From: Joe Perches
Convert the struct dvb_pll_desc uses to const and
change the "entries" fixed array size from 12 to []
It saves a couple KB overall and remove ~5KB of data.
$ size drivers/media/dvb-frontends/dvb-pll.o*
textdata bss dec hex filename
85201552
Hi Maruro and linux-media folks,
This patchset adds support for a LinuxDVB demux driver for the
ST STB stih407 family SoC's. Mauro - it is what I spoke to you about
when we met at ELC-E in Dusseldorf last year.
One big advantage of having a upstream demux driver for ST
SoC's is that it will be ea
When using stv0367 demodulator with STi STB platforms,
we can have easily have four or more stv0367 demods running
in the system at one time.
As typically the b2120 reference design ships with a b2004a daughter
board, which can accept two dvb NIM cards, and each b2100A NIM
has 2x stv0367 demods an
This patch adds the DT bindings documentation for the c8sectpfe LinuxDVB
demux driver whose IP is in the STiH407 family silicon SoC's.
Signed-off-by: Peter Griffin
---
.../bindings/media/stih407-c8sectpfe.txt | 89 ++
include/dt-bindings/media/c8sectpfe.h
The B2100A dvb NIM card from ST has 2x stv0367 demodulators
and 2x TDA18212 silicon tuners, with a 16Mhz crystal. To
get this working properly with the upstream driver we need
to add support for the 16Mhz reference clock.
Signed-off-by: Peter Griffin
---
drivers/media/dvb-frontends/stv0367.c | 5
[+cc Jingoo, Pratyush]
On Thu, Jul 30, 2015 at 04:50:55PM +, Gabriele Paoloni wrote:
> > -Original Message-
> > From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> > ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> > Sent: Thursday, July 30, 2015 5:15 PM
> > To: Gabriele Paol
These functions are used by the core code for creating the LDVB
devices and adapter.
Addtionally some older SoC's (and potentially newer ones) have different
frontend HW which would allow those devices to be easily supported
in the future by keeping the code specific to the IP separate from the
mo
This patch adds support for the following 2 NIM cards: -
1) B2100A (2x stv0367 demods & 2x NXP tda18212 tuners)
2) STV0903-6110NIM (stv0903 demod + 6110 tuner, lnb24)
A NIM card is a cold plugable expansion card which usually
features a demodulator / tuner combination.
Signed-off-by: Peter Griffi
This patch adds the Kconfig and Makefile for the c8sectpfe driver
so it will be built. It also selects additional demodulator and tuners
which are required by the supported NIM cards.
Signed-off-by: Peter Griffin
---
drivers/media/platform/Kconfig| 4 +++-
drivers/media/platform
Add the new c8sectpfe demux driver to the STi section of the
MAINTAINERS file.
Signed-off-by: Peter Griffin
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a226416..a9f2f37 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1506,6 +1506,7 @@ F:
This patch adds in the required DT node for the c8sectpfe
Linux DVB demux driver which allows the tsin channels
to be used on an upstream kernel.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stihxxx-b2120.dtsi | 38
1 file changed, 38 insertions(+)
dif
This patch adds support for the c8sectpfe input HW found on
STiH407/410 SoC's.
It currently supports the TS input block, memdma engine
and hw PID filtering blocks of the C8SECTPFE subsystem.
The driver creates one LinuxDVB adapter, and a
demux/dvr/frontend set of devices for each tsin channel
whi
Some basic debugfs support to dump the IP registers. Further
statistics could easily be added in the future for example for
each enabled tsin channel we could expose number of corrupt packets
received etc.
Signed-off-by: Peter Griffin
---
.../platform/sti/c8sectpfe/c8sectpfe-debugfs.c | 271
More platform specific extended opp bindings will follow and it would be
easy to manage them with a directory for opp. Lets create that and move
the existing opp bindings into it.
Signed-off-by: Viresh Kumar
---
Resending to get cc list fixed, which isn't getting populated due to a
bug with get_m
On 30-07-15, 11:24, Rob Herring wrote:
> On Thu, Jul 30, 2015 at 8:49 AM, Viresh Kumar wrote:
> > On 30-07-15, 08:18, Rob Herring wrote:
> >> On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar
> >> wrote:
> >> > More platform specific extended opp bindings will follow and it would be
> >> > easy to m
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> Sent: Thursday, July 30, 2015 5:15 PM
> To: Gabriele Paoloni
> Cc: Rob Herring; a...@arndb.de; lorenzo.pieral...@arm.com; Wangzhou (B);
> robh...@kernel.or
Le 20/07/2015 14:37, Nicolas Ferre a écrit :
> Le 20/07/2015 11:32, Josh Wu a écrit :
>> They'll use "atmel,sama5d3-rstc" for reset function.
>>
>> Cc: devicetree@vger.kernel.org
>> Signed-off-by: Josh Wu
>
> Acked-by: Nicolas Ferre
>
> And we'll have to synchronize with the other patches. The
On Thu 30 Jul 08:26 PDT 2015, Rob Herring wrote:
> On Wed, Jul 29, 2015 at 6:51 PM, Bjorn Andersson
> wrote:
> > On Fri 24 Jul 08:29 PDT 2015, Rob Herring wrote:
[..]
> > As we're trying to specify a default brightness within the range [0,
> > max_brightness) the latter doesn't make much sense.
>
On Thu, Jul 30, 2015 at 8:49 AM, Viresh Kumar wrote:
> On 30-07-15, 08:18, Rob Herring wrote:
>> On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar
>> wrote:
>> > More platform specific extended opp bindings will follow and it would be
>> > easy to manage them with a directory for opp. Lets create th
On Mi, 2015-07-29 at 17:03 +0800, Haibo Chen wrote:
> tuning-step is the delay cell steps in tuning procedure. The default
> value of tuning-step is 1. For imx6 series usdhc, tuning procedure can
> be passed when the tuning-step value is 1. But imx7d usdhc need the
> tuning-step value as 2, otherwi
On Thu, Jul 30, 2015 at 3:46 AM, Lee Jones wrote:
> On Wed, 29 Jul 2015, Stephen Boyd wrote:
>
>> On 07/29, Lee Jones wrote:
>> > On Tue, 28 Jul 2015, Stephen Boyd wrote:
>> >
>> > > On 07/28, Viresh Kumar wrote:
>> > > > Cc'ing few people (whom I cc'd last time as well :)).
>> > > >
>> > > > On 2
On Thu, Jul 30, 2015 at 01:52:13PM +, Gabriele Paoloni wrote:
>
>
> > -Original Message-
> > From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> > ow...@vger.kernel.org] On Behalf Of Rob Herring
> > Sent: Thursday, July 30, 2015 2:43 PM
> > To: Gabriele Paoloni
> > Cc: Bjorn He
Hi Stefan,
Le Mon, 27 Jul 2015 18:42:41 +0200, Stefan Agner a
écrit :
> This driver supports Freescale NFC (NAND flash controller) found on
> Vybrid (VF610), MPC5125, MCF54418 and Kinetis K70. The driver has
> been tested on 8-bit and 16-bit NAND interface and supports ONFI
> parameter page read
On Thu, Jul 30, 2015 at 08:42:53AM -0500, Rob Herring wrote:
> On Wed, Jul 29, 2015 at 2:44 PM, Gabriele Paoloni
> wrote:
> > Hi Bjorn
> >
> > Many Thanks for your reply
> >
> > I have commented back inline with resolutions from my side.
> >
> > If you're ok with them I'll send it out a new versio
Regards,
Igal Liberman.
> -Original Message-
> From: Wood Scott-B07421
> Sent: Friday, June 19, 2015 5:49 AM
> To: Mike Turquette; Tang Yuantian-B29983
> Cc: Rafael J. Wysocki; Liberman Igal-B31950; Bucur Madalin-Cristian-B32716;
> linux-...@vger.kernel.org; linux...@vger.kernel.org; linu
Hey Mark,
On Wed, Jul 29 2015 at 10:40 -0600, Mark Rutland wrote:
On Tue, Jul 28, 2015 at 08:38:33PM +0100, Lina Iyer wrote:
Hello,
I am looking to find a way to uniquely identify a device in the driver.
Here is an example -
big: power-controller@1 {
compatible = "soc,
> On 30.07.2015, at 09:10, Martin Sperl wrote:
>> What about adding “bcrm,bcm2835-aux-enable” to drivers/mfd/syscon.c
>> compatibility?
>>
>> That way we:
>> * have a clean dt that only represents hardware
>> * reuse existing code with minimal modifications
>> * minimal effort
>>
>> That would
On Wed, Jul 29, 2015 at 6:51 PM, Bjorn Andersson
wrote:
> On Fri 24 Jul 08:29 PDT 2015, Rob Herring wrote:
>
>> On Thu, Jul 23, 2015 at 2:52 PM, Bjorn Andersson
>> wrote:
>> > Add the possibility of specifying the default brightness in DT.
>> >
>> > Signed-off-by: Bjorn Andersson
>> > ---
>> >
>
On 07/29/2015 07:38 PM, Sören Brinkmann wrote:
> On Tue, 2015-07-28 at 11:14PM -0700, Moritz Fischer wrote:
>> Hi Sören,
>>
>> On Tue, Jul 28, 2015 at 3:53 PM, Sören Brinkmann
>> wrote:
>>> On Mon, 2015-07-27 at 09:52PM -0700, Moritz Fischer wrote:
Hi Sören,
thanks for your feedback
Hi Michael,
On Thu, 30 Jul 2015, Michael Ira Krufky wrote:
> On Thu, Jul 30, 2015 at 7:14 AM, Michael Ira Krufky
> wrote:
> > On Thu, Jul 30, 2015 at 6:08 AM, Joe Perches wrote:
> >> On Thu, 2015-07-30 at 10:47 +0100, Peter Griffin wrote:
> >>> Hi Mauro / Joe,
> >>>
> >>> On Wed, 22 Jul 2015,
Hi Michael,
On Thu, 30 Jul 2015, Michael Ira Krufky wrote:
> On Thu, Jul 30, 2015 at 7:14 AM, Michael Ira Krufky
> wrote:
> > On Thu, Jul 30, 2015 at 6:08 AM, Joe Perches wrote:
> >> On Thu, 2015-07-30 at 10:47 +0100, Peter Griffin wrote:
> >>> Hi Mauro / Joe,
> >>>
> >>> On Wed, 22 Jul 2015,
Add driver for Samsung S3FWRN5 NFC controller.
S3FWRN5 is using NCI protocol and I2C communication interface.
Signed-off-by: Robert Baldyga
---
Changelog:
v2:
- Adressed comments from Paul Bolle
v1: http://www.spinics.net/lists/kernel/msg2044290.html
.../devicetree/bindings/net/nfc/s3fwrn5.t
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Gabriele Paoloni
> Sent: Thursday, July 30, 2015 2:52 PM
> To: Rob Herring
> Cc: Bjorn Helgaas; a...@arndb.de; lorenzo.pieral...@arm.com; Wangzhou
> (B); robh...@kernel.or
On Thu, Jul 30, 2015 at 09:46:58AM +0800, Li Jun wrote:
> On Wed, Jul 29, 2015 at 09:11:41PM -0500, Felipe Balbi wrote:
> > On Thu, Jul 30, 2015 at 07:24:03AM +0800, Li Jun wrote:
> > > On Wed, Jul 29, 2015 at 10:04:27AM -0500, Felipe Balbi wrote:
> > > > On Mon, Jul 27, 2015 at 03:21:59PM +0800, P
On 07/30/2015 12:22 PM, Paul Bolle wrote:
> On wo, 2015-07-29 at 14:15 +0200, Robert Baldyga wrote:
>> --- /dev/null
>> +++ b/drivers/nfc/s3fwrn5/Kconfig
>> @@ -0,0 +1,22 @@
>> +config NFC_S3FWRN5
>> +tristate "Samsung S3FWRN5 NFC driver"
>> +depends on NFC_NCI
>> +default n
>> +---
On Thu, 2015-07-30 at 15:36 +0200, Nicolas Ferre wrote:
> Le 30/07/2015 15:06, Andy Shevchenko a écrit :
> > This change documents a new property for the Atmel serial device,
> > allowing an
> > implementer to specify either four bytes or one byte access to the
> > controller
> > data register.
>
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Rob Herring
> Sent: Thursday, July 30, 2015 2:43 PM
> To: Gabriele Paoloni
> Cc: Bjorn Helgaas; a...@arndb.de; lorenzo.pieral...@arm.com; Wangzhou
> (B); robh...@kernel.or
On 30-07-15, 08:18, Rob Herring wrote:
> On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar wrote:
> > More platform specific extended opp bindings will follow and it would be
> > easy to manage them with a directory for opp. Lets create that and move
> > the existing opp bindings into it.
> >
> > Cc:
On Wed, Jul 29, 2015 at 2:44 PM, Gabriele Paoloni
wrote:
> Hi Bjorn
>
> Many Thanks for your reply
>
> I have commented back inline with resolutions from my side.
>
> If you're ok with them I'll send it out a new version in the appropriate
> patchset
>
> Cheers
>
> Gab
>
>> -Original Message-
Le 30/07/2015 15:06, Andy Shevchenko a écrit :
> This change documents a new property for the Atmel serial device, allowing an
> implementer to specify either four bytes or one byte access to the controller
> data register.
>
> This supports a change that unbreaks this driver on ATNGW100 board.
>
On Thu, 30 Jul 2015, Paul Bolle wrote:
> On do, 2015-07-30 at 12:45 +0100, Lee Jones wrote:
> > On Wed, 29 Jul 2015, Paul Bolle wrote:
> > > Besides, if I read sti_max_probe() correctly, without OF support
> > > loading
> > > this module won't accomplish much. So what would another way of
> > > au
Signed-off-by: Robert ABEL
---
kernel/resource.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/kernel/resource.c b/kernel/resource.c
index 0bcebff..b4c9b27 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -236,6 +236,13 @@ static int __release_resource(struct resource *old)
This patch prevents a kernel OOPS when removing a DT overlay containing
nodes with reg properties. release_resources is called for these nodes.
However, the resource structs were never initialized, hence the kernel OOPS.
This is obviously a stopgap measure until a proper solution is coded, see [1
On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar wrote:
> With a 32 bit value, the maximum frequency that the bindings can
> support is ~ 4 GHz. And that might fall short of what newer systems may
> have.
4GHz should be fast enough for anyone...
> Allow opp-hz to be a 64 bit big-endian value.
>
> C
These Ux500 clocks have been around for years and were never
properly documented. Add the proper binding documentation.
Cc: Ulf Hansson
Signed-off-by: Linus Walleij
---
Ulf/Mike: please ACK this patch so I can take it through
ARM SoC.
---
Documentation/devicetree/bindings/clock/ux500.txt | 64 +
On Wed, Jul 29, 2015 at 5:52 AM, Viresh Kumar wrote:
> More platform specific extended opp bindings will follow and it would be
> easy to manage them with a directory for opp. Lets create that and move
> the existing opp bindings into it.
>
> Cc: Rob Herring
Use get_maintainers.pl please so you
The commit b5199d468177 (tty/serial: at91: add support to FIFOs) changed data
stream 32-bit accesses in the driver to 8-bit. This, unfortunately, breaks data
register access on ATNGW100, where the IP needs data register accesses to be
long accesses (all other accesses appear to be OK).
This change
This change documents a new property for the Atmel serial device, allowing an
implementer to specify either four bytes or one byte access to the controller
data register.
This supports a change that unbreaks this driver on ATNGW100 board.
Signed-off-by: Andy Shevchenko
---
Documentation/devicet
On do, 2015-07-30 at 12:45 +0100, Lee Jones wrote:
> On Wed, 29 Jul 2015, Paul Bolle wrote:
> > Besides, if I read sti_max_probe() correctly, without OF support
> > loading
> > this module won't accomplish much. So what would another way of
> > autoloading this module buy you?
>
> I think this lin
Hi All,
On Thu, Jul 30, 2015 at 5:41 PM, Rameshwar Prasad Sahu wrote:
> This patch adds test case for APM X-Gene SoC CRC32C algorithm.
Please discard this patch description and subject line in this cover
letter, I have resent it again.
Thanks,
Ram
>
> Signed-off-by: Rameshwar Prasad Sahu
> --
This patch implements support for APM X-Gene SoC CRC32C h/w accelerator driver
and adds CRC32C support in dmaengine framework. APM X-Gene SoC has DMA engine
capable of performing CRC32C.
Signed-off-by: Rameshwar Prasad Sahu
---
Rameshwar Prasad Sahu (4):
dmaengine: Add support for new feature
1 - 100 of 167 matches
Mail list logo
