To connect the channel of USB-DMAC to USBHS DnFIFO number, this patch
adds this channel/FIFO number in dma-names. Otherwise, this driver
needs to add analysis code for device tree.
Signed-off-by: Yoshihiro Shimoda
---
.../devicetree/bindings/usb/renesas_usbhs.txt| 5 -
drivers/usb/r
This patch set is based on Felipe's usb.git / testing/next branch.
(commit id = 9024c495f35be735a917571406fab30a789c27d1)
To use the USB-DMAC, we have to add some device nodes for USB-DMAC
in dts file. If we don't have such device nodes, this driver will
use PIO.
Changes from v2:
- Remove patch
This patch fixes the setup sequence in xfer_work(). Otherwise,
sometimes a usb transaction will get stuck.
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/renesas_usbhs/fifo.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/renesas_usbhs/fifo.c b/drivers/usb/
Some Renesas SoCs have the USB-DMAC. It is able to terminate transfers
when a short packet is received, even if less bytes than the transfer
counter size have been received. Also, it is able to send a short
packet even if the packet size is not multiples of 8bytes.
Since the previous code has used
From: Frank Rowand
Fix an of_unittest.c include path to account for the move of
unittest.c into unittest-data/.
Signed-off-by: Frank Rowand
---
drivers/of/unittest-data/unittest.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/of/unittest-data/unittest.c
==
From: Frank Rowand
Move of_unittest.c into unittest-data/
This is based on v4.0-rc3.
All checkpatch errors are ignored, as this is just a file move. At least
two of the checkpatch errors appear to be real bugs, to be addressed in
a future patch.
Signed-off-by: Frank Rowand
---
drivers/of/u
From: Frank Rowand
This 3 patch series is not bisectable. If CONFIG_OF_UNITTEST=y then the kernel
will not build with just patch 1 or just patches 1 and 2 applied.
If CONFIG_OF_UNITTEST=y then a kernel image make will always cause .version to
be incremented, even if there are not source changes
Hi,
> On Thu, Mar 12, 2015 at 04:33:41AM +, yoshihiro shimoda wrote:
> > Hi Geert-san again,
> >
> > > Hi Geert-san,
> > >
> > > Thank you for the reply again!
> > >
> > > > Hi Shimoda-san,
> > > >
> > > > On Mon, Feb 16, 2015 at 2:52 AM, Yoshihiro Shimoda
> > > > wrote:
> > > > > According t
From: Frank Rowand
Fix an of_unittest.c include path to account for the move of
unittest.c into unittest-data/.
Signed-off-by: Frank Rowand
---
drivers/of/unittest-data/unittest.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/of/unittest-data/unittest.c
==
From: Frank Rowand
Move of_unittest.c into unittest-data/
This is based on v4.0-rc3.
All checkpatch errors are ignored, as this is just a file move. At least
two of the checkpatch errors appear to be real bugs, to be addressed in
a future patch.
Signed-off-by: Frank Rowand
---
drivers/of/u
From: Frank Rowand
This 3 patch series is not bisectable. If CONFIG_OF_UNITTEST=y then the kernel
will not build with just patch 1 or just patches 1 and 2 applied.
If CONFIG_OF_UNITTEST=y then a kernel image make will always cause .version to
be incremented, even if there are not source changes
Hi,
On Thu, Mar 12, 2015 at 04:33:41AM +, yoshihiro shimoda wrote:
> Hi Geert-san again,
>
> > Hi Geert-san,
> >
> > Thank you for the reply again!
> >
> > > Hi Shimoda-san,
> > >
> > > On Mon, Feb 16, 2015 at 2:52 AM, Yoshihiro Shimoda
> > > wrote:
> > > > According to the gadget.h, a "co
Hi Geert-san again,
> Hi Geert-san,
>
> Thank you for the reply again!
>
> > Hi Shimoda-san,
> >
> > On Mon, Feb 16, 2015 at 2:52 AM, Yoshihiro Shimoda
> > wrote:
> > > According to the gadget.h, a "complete" function will always be called
> > > with interrupts disabled. However, sometimes usbh
Hi Marc,
On Wed, Mar 11, 2015 at 11:47 PM, Marc Zyngier wrote:
> On 11/03/15 17:57, Feng Kan wrote:
>> On Wed, Mar 11, 2015 at 10:31 AM, Marc Zyngier wrote:
>>> On 11/03/15 17:19, Feng Kan wrote:
On Wed, Mar 11, 2015 at 7:53 AM, Marc Zyngier wrote:
> On 27/01/15 07:03, Pranavkumar Sawa
On Thu, Mar 12, 2015 at 09:54:18AM +0800, Peter Chen wrote:
> On Wed, Mar 11, 2015 at 09:24:25AM +0800, Shawn Guo wrote:
> > On Fri, Mar 06, 2015 at 04:04:20PM +0800, Peter Chen wrote:
> > > USB vbus 5V is from PMIC SWBST, so set swbst_reg as vbus's
> > > parent reg, it fixed a bug that the voltage
This adds the binding documentation for the Imagination Technologies hash
accelerator that provides hardware acceleration for SHA1/SHA224/SHA256/MD5
hashes. This hardware will be present in the upcoming pistachio SoC.
Signed-off-by: James Hartley
---
.../devicetree/bindings/crypto/img-hash.txt
This adds support for the Imagination Technologies hash accelerator which
provides hardware acceleration for SHA1 SHA224 SHA256 and MD5 hashes.
Signed-off-by: James Hartley
---
drivers/crypto/Kconfig| 14 +
drivers/crypto/Makefile |1 +
drivers/crypto/img-hash.c | 1028 ++
This adds support for the Imagination Technologies hash accelerator which
provides hardware acceleration for SHA1 SHA244 SHA256 and MD5 hashes.
Tested on silicon, using testmgr.
Changes from V3:
* Standardised the cra_priorities to 300, sufficient to be chosen
ahead of software
On Wed, Mar 11, 2015 at 09:24:25AM +0800, Shawn Guo wrote:
> On Fri, Mar 06, 2015 at 04:04:20PM +0800, Peter Chen wrote:
> > USB vbus 5V is from PMIC SWBST, so set swbst_reg as vbus's
> > parent reg, it fixed a bug that the voltage of vbus is incorrect
> > due to swbst_reg is disabled after boots u
Paul Bolle writes:
> [Added Rusty and Dave.]
>
> On Sat, 2015-03-07 at 20:51 -0800, Dmitry Torokhov wrote:
>> On Sat, Mar 07, 2015 at 11:38:55PM +0100, Paul Bolle wrote:
>> > From a technological standpoint it would be easy to declare "GPL" (or
>> > any other string) to mean "GPL v2 compatible", w
Paul,
On Wed, Mar 11, 2015 at 4:18 PM, Paul Bolle wrote:
> MODULE_DEVICE_TABLE() is defined only in include/linux/module.h. The few
> related lines read (in next-20150311):
> #ifdef MODULE
> /* Creates an alias so file2alias.c can find device table. */
> #define MODU
On Fri, Mar 06, 2015 at 06:55:14PM +0100, Jan Lübbe wrote:
> On Do, 2015-03-05 at 10:34 +1100, David Gibson wrote:
> > On Fri, Feb 27, 2015 at 08:55:45PM +0200, Pantelis Antoniou wrote:
> > > Enables the generation of a __fixups__ node for trees compiled
> > > using the -@ option that are using the
Add documentation for generic SYSCON poweroff driver.
Signed-off-by: Moritz Fischer
---
.../bindings/power/reset/syscon-poweroff.txt | 23 ++
1 file changed, 23 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/reset/syscon-poweroff.txt
b/Documentatio
Add a generic SYSCON register mapped poweroff mechanism.
Signed-off-by: Moritz Fischer
---
drivers/power/reset/Kconfig | 7 +++
drivers/power/reset/Makefile | 1 +
drivers/power/reset/syscon-poweroff.c | 102 ++
3 files changed, 110 insertio
This patchset adds support for generic register mapped poweroff via SYCON.
v3:
- Fixed OF dependecies (again) as suggested by Sebastian
- Remove (more) module specific stuff as suggested by Paul
v2:
- Fixed documentation copy & paste
- Deal with OF dependecies as suggested by Sebastian
- Rem
Hi Moritz,
On Wed, Mar 11, 2015 at 03:32:24PM -0700, Moritz Fischer wrote:
> [...]
> +static struct platform_driver syscon_poweroff_driver = {
> + .probe = syscon_poweroff_probe,
> + .remove = syscon_poweroff_remove,
> + .driver = {
> + .name = "syscon-poweroff",
> +
Hi Sakari,
Thank you for the patch.
On Saturday 07 March 2015 23:41:12 Sakari Ailus wrote:
> Add the ISP device to omap3 DT include file and add support to the driver to
> use it.
>
> Also obtain information on the external entities and the ISP configuration
> related to them through the Device
Hi Sakari,
Thank you for the patch.
On Saturday 07 March 2015 23:41:11 Sakari Ailus wrote:
> Signed-off-by: Sakari Ailus
> ---
> .../devicetree/bindings/media/ti,omap3isp.txt | 64 +
> MAINTAINERS|1 +
> 2 files changed, 65 inse
Am Mittwoch, 11. März 2015, 15:15:17 schrieb Doug Anderson:
> Specifying these rails should eventually let us do UHS.
>
> Signed-off-by: Doug Anderson
This one looks good to me and I'll take it into my dts branch.
But due to the deferal issue fixed in patch1, I'll wait a bit for patch1
hopeful
but I don't think those macros are used.
> >> +MODULE_DEVICE_TABLE(of, syscon_poweroff_of_match);
> >
> > This will be preprocessed away.
>
> In my experiments it didn't work without this, are you sure it's not needed?
MODULE_DEVICE_TABL
Hi Sakari,
Thank you for the patch.
On Saturday 07 March 2015 23:41:03 Sakari Ailus wrote:
> Make omap3isp configuration data structures more suitable for consumption by
> the DT by separating the I2C bus information of all the sub-devices in a
> group and the ISP bus information from each other.
Hi Laurent,
On Wed, Mar 11, 2015 at 08:09:11PM +0200, Laurent Pinchart wrote:
> Hi Sakari,
>
> On Wednesday 11 March 2015 13:04:43 Sakari Ailus wrote:
> > On Sun, Mar 08, 2015 at 11:33:27AM +, Lad Prabhakar wrote:
> > > From: Benoit Parrot
> > >
> > > this patch adds support for omnivision'
On Wed, Mar 11, 2015 at 11:22:46PM +0100, Marek Vasut wrote:
> On Wednesday, March 11, 2015 at 10:57:25 PM, Brian Norris wrote:
> > Almost all flash that are "compatible" with m25p80 support the JEDEC
> > READ ID opcode (0x95)
>
> On the 2/2 patch, you claim READ ID is 0x9F . You might want to sor
Add a generic SYSCON register mapped poweroff mechanism.
Signed-off-by: Moritz Fischer
---
drivers/power/reset/Kconfig | 7 +++
drivers/power/reset/Makefile | 1 +
drivers/power/reset/syscon-poweroff.c | 97 +++
3 files changed, 105 insertions
This patchset adds support for generic register mapped poweroff via SYCON.
v2:
- Fixed documentation copy & paste
- Deal with OF dependecies as suggested by Sebastian
- Remove module specific stuff as suggested by Paul
v1:
- Earlier versions of this were specific to our product, however,
a
Add documentation for generic SYSCON poweroff driver.
Signed-off-by: Moritz Fischer
---
.../bindings/power/reset/syscon-poweroff.txt | 23 ++
1 file changed, 23 insertions(+)
diff --git a/Documentation/devicetree/bindings/power/reset/syscon-poweroff.txt
b/Documentatio
On Wednesday, March 11, 2015 at 10:57:25 PM, Brian Norris wrote:
> Almost all flash that are "compatible" with m25p80 support the JEDEC
> READ ID opcode (0x95)
On the 2/2 patch, you claim READ ID is 0x9F . You might want to sort
this inconsistency :) Otherwise ...
Reviewed-by: Marek Vasut
Best
Specifying these rails should eventually let us do UHS.
Signed-off-by: Doug Anderson
---
Changes in v4:
- Add vcc_sd regulator which is present on EVB 2.0 boards
Changes in v3: None
Changes in v2:
- Fix subject line
arch/arm/boot/dts/rk3288-evb.dtsi | 23 +++
1 file changed
Heiko,
On Tue, Jan 6, 2015 at 9:44 AM, Heiko Stübner wrote:
> Hi Doug,
>
> Am Montag, 15. Dezember 2014, 16:22:20 schrieb Doug Anderson:
>> Specifying these rails should eventually let us do UHS.
>>
>> Signed-off-by: Doug Anderson
>> ---
>> Changes in v3: None
>> Changes in v2:
>> - Fix subject
On Wednesday 11 March 2015 02:27:08 Chunyan Zhang wrote:
> This patchset adds Spreadtrum's Sharkl64 support in arm64 device tree.
>
> Changes from v7:
> - Added Mark Rutland's Acked-by
> - Rebased v4.0-rc1
>
Applied both to next/arm64.
I had some trouble applying the patches bec
Paul,
thanks for your feedback. While developing this I looked at other drivers in
the tree and many of your comments would apply to them, too?
On Wed, Mar 11, 2015 at 2:31 AM, Paul Bolle > +config POWER_RESET_SYSCON_POWEROFF
>> + bool "Generic SYSCON regmap poweroff driver"
>
> This adds a b
On Monday 09 March 2015 09:41:04 Michal Simek wrote:
> Initial version of device tree for Xilinx ZynqMP SoC.
>
> Signed-off-by: Michal Simek
> Acked-by: Sören Brinkmann
>
Pulled into next/arm64, thanks!
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
t
Almost all flash that are "compatible" with m25p80 support the JEDEC
READ ID opcode (0x95), and in fact, that is often the only thing that is
used to differentiate them. Let's add a compatible string that
represents this lowest common denominator of compatibility.
Device trees can still specify ma
Use the new 'nor-jedec' binding to provide automatic detection of flash
that use the 0x9F READ ID opcode. This can help for use cases where
platforms just specify compatibility with "m25p80", and then see
messages like this:
m25p80 spi32766.0: found s25fl256s1, expected m25p80
Instead, they can
From: Florian Fainelli
Date: Tue, 10 Mar 2015 16:57:10 -0700
> This patch series completes the PHY reads/writes diversion when we
> need to use the slave MII bus provided by DSA and the underlying
> switch drivers to implement the real PHY reads and writes. This is
> particularly useful when they
On Wednesday 11 March 2015 14:37:58 Arun Ramamurthy wrote:
> On 15-03-10 01:27 PM, Arnd Bergmann wrote:
> > On Wednesday 25 February 2015 16:24:06 Arun Ramamurthy wrote:
> > Should I run this by Alan Stern?
>
> I've added him to Cc here. He clearly didn't know the background about
> >
On Wednesday 11 March 2015 15:35:22 Kumar Gala wrote:
> On Mar 11, 2015, at 3:20 PM, Arnd Bergmann wrote:
>
> > On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
> >>
> >> But are these values actually used by the boot loader?
> >>
> >> As far as I could see in 8974 the dtbTool provide
On Wednesday 11 March 2015 13:00:22 Arun Ramamurthy wrote:
>
> Arnd, this is the device tree entry that I would end up with and I plan
> to use syscon_regmap_lookup_by_phandle in the rtc driver. Does this look
> acceptable?
>
> rtc: iproc_rtc@0x03026000 {
> compatible = "brcm,ip
On 15-03-10 01:27 PM, Arnd Bergmann wrote:
On Wednesday 25 February 2015 16:24:06 Arun Ramamurthy wrote:
Should I run this by Alan Stern?
I've added him to Cc here. He clearly didn't know the background about
the DT binding change, and should not need to, but he may have an opinion
on what n
Add qcom,msm-id and qcom,board-id to allow bootloader to identify which
device tree to boot on the MTP8916 boards.
Signed-off-by: Kumar Gala
---
arch/arm64/boot/dts/qcom/msm8916-mtp.dts | 3 +++
arch/arm64/boot/dts/qcom/msm8916.dtsi| 5 +
2 files changed, 8 insertions(+)
diff --git a/ar
Add initial device tree support for Qualcomm MSM8916 SoC and MTP8916
evaluation board. At the current time we only boot up a single processor.
Signed-off-by: Kumar Gala
---
v3:
* Removed qcom,msm-id and qcom,board-id
* Added top level compat for "qcom,msm8916-mtp-smb1360"
v2:
* Updated to dropp
The top level qcom,msm-id and qcom,board-id are utilized by bootloaders
on Qualcomm MSM platforms to determine which device tree should be
utilized and passed to the kernel.
Cc:
Signed-off-by: Kumar Gala
---
Documentation/devicetree/bindings/arm/msm/ids.txt | 65 +++
include
On Mar 11, 2015, at 3:20 PM, Arnd Bergmann wrote:
> On Wednesday 11 March 2015 08:33:04 Bjorn Andersson wrote:
>>
>> But are these values actually used by the boot loader?
>>
>> As far as I could see in 8974 the dtbTool provided by Qualcomm
>> extracts the values from the list of dtbs and use
On 03/11/2015 11:59 AM, Rob Herring wrote:
On Wed, Mar 11, 2015 at 10:28 AM, Murali Karicheri wrote:
On 03/11/2015 08:49 AM, Russell King - ARM Linux wrote:
On Wed, Mar 11, 2015 at 07:35:45AM -0500, Rob Herring wrote:
On Tue, Mar 10, 2015 at 10:25 AM, Murali Karicheri
wrote:
On some platf
Hi Prabhakar,
On Wednesday 11 March 2015 19:40:13 Lad, Prabhakar wrote:
> On Wed, Mar 11, 2015 at 6:22 PM, Laurent Pinchart wrote:
> > On Tuesday 10 March 2015 03:35:57 Sakari Ailus wrote:
> >> On Sun, Mar 08, 2015 at 11:33:27AM +, Lad Prabhakar wrote:
> >> ...
> >>
> >> > +static struct ov26
On 15-03-04 02:58 PM, Arnd Bergmann wrote:
On Wednesday 04 March 2015 14:53:40 Arun Ramamurthy wrote:
On 15-03-04 02:50 PM, Arnd Bergmann wrote:
On Wednesday 04 March 2015 14:40:13 Arun Ramamurthy wrote:
On 15-03-04 02:21 PM, Arnd Bergmann wrote:
On Thursday 12 February 2015 14:17:41 Arun R
* Sebastian Reichel [150311 12:37]:
> Hi,
>
> On Wed, Mar 11, 2015 at 10:43:17AM -0700, Tony Lindgren wrote:
> > No no, "capacity-uah" is what we should use, but you need an ack from
> > the battery and device tree people that this is OK. Let's not add
> > "ti,capacity-uah” as that can obviously
Hi Laurent,
Thanks for the review.
On Wed, Mar 11, 2015 at 6:22 PM, Laurent Pinchart
wrote:
> On Tuesday 10 March 2015 03:35:57 Sakari Ailus wrote:
>> On Sun, Mar 08, 2015 at 11:33:27AM +, Lad Prabhakar wrote:
>> ...
>>
>> > +static struct ov2659_platform_data *
>> > +ov2659_get_pdata(struct
On 03/11/2015 12:32 PM, Tony Lindgren wrote:
> * Suman Anna [150311 10:18]:
>> On 03/11/2015 11:26 AM, Tony Lindgren wrote:
>>> * Dave Gerlach [150310 12:55]:
Suman and I have been looking at this together, so I can comment here. An
implementation like this is what Suman is referring to
On Tuesday 10 March 2015 03:35:57 Sakari Ailus wrote:
> On Sun, Mar 08, 2015 at 11:33:27AM +, Lad Prabhakar wrote:
> ...
>
> > +static struct ov2659_platform_data *
> > +ov2659_get_pdata(struct i2c_client *client)
> > +{
> > + struct ov2659_platform_data *pdata;
> > + struct device_node *e
On 11/03/15 17:57, Feng Kan wrote:
> On Wed, Mar 11, 2015 at 10:31 AM, Marc Zyngier wrote:
>> On 11/03/15 17:19, Feng Kan wrote:
>>> On Wed, Mar 11, 2015 at 7:53 AM, Marc Zyngier wrote:
On 27/01/15 07:03, Pranavkumar Sawargaonkar wrote:
> In APM X-Gene, GIC register space is 64K aligned
On 03/09/15 08:16, Lina Iyer wrote:
> Register cpuidle ops for Krait Processor Sub-System.
> Supports v1 and v2 versions of KPSS.
>
> Cc: Stephen Boyd
> Cc: Arnd Bergmann
> Cc: Kevin Hilman
> Cc: Daniel Lezcano
> Signed-off-by: Lina Iyer
> ---
> arch/arm/include/asm/cpuidle_ops.h | 5 +
>
Hi Sakari,
On Wednesday 11 March 2015 13:04:43 Sakari Ailus wrote:
> On Sun, Mar 08, 2015 at 11:33:27AM +, Lad Prabhakar wrote:
> > From: Benoit Parrot
> >
> > this patch adds support for omnivision's ov2659
> > sensor, the driver supports following features:
> > 1: Asynchronous probing
> >
Document the Broadcom iProc PCIe platform interface device tree binding
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
.../devicetree/bindings/pci/brcm,iproc-pcie.txt| 63
1 file changed, 63 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pc
This adds the support for Broadcom iProc PCIe controller
pcie-iproc.c servers as the common core driver, and front-end bus
interface needs to be added to support different bus interfaces
pcie-iproc-pltfm.c contains the support for the platform bus interface
Signed-off-by: Ray Jui
Reviewed-by: S
Export symbols of the following PCI functions so they can be referenced
by a PCI driver compiled as a kernel loadable module:
pci_common_swizzle
pci_create_root_bus
pci_stop_root_bus
pci_remove_root_bus
pci_assign_unassigned_bus_resources
pci_fixup_irqs
Signed-off-by: Ray Jui
---
drivers/pci/pc
Add PCIe device nodes in bcm-cygnus.dtsi but keep them disabled there.
Only enable them for bcm958300k where PCIe interfaces are populated
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm/boot/dts/bcm-cygnus.dtsi | 42 +
arch/arm/boot/dts/bcm9
This patch series adds the support for Broadcom iProc PCIe controller
pcie-iproc.c servers as the common core driver, and front-end bus
interface needs to be added to support different bus interfaces
pcie-iproc-pltfm.c contains the support for the platform bus interface
Changes from v5:
- Sync
On Wed, Mar 11, 2015 at 10:31 AM, Marc Zyngier wrote:
> On 11/03/15 17:19, Feng Kan wrote:
>> On Wed, Mar 11, 2015 at 7:53 AM, Marc Zyngier wrote:
>>> On 27/01/15 07:03, Pranavkumar Sawargaonkar wrote:
In APM X-Gene, GIC register space is 64K aligned while the sizes mentioned
in the dt
On Sun, Mar 08, 2015 at 10:13:57PM +0100, Hans de Goede wrote:
> On sun4i-a10, when GPIOs are configured as external interrupt the value for
> them in the data register does not seem to get updated, so set their mux to
> input (and restore afterwards) when reading the pin.
>
> Missed edges seem to
* Dr. H. Nikolaus Schaller [150311 10:13]:
> Am 11.03.2015 um 17:44 schrieb Tony Lindgren :
> > * Dr. H. Nikolaus Schaller [150311 09:17]:
> >> Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
> >>>
> >>> Rather than just making platform_data into device tree properties..
> >>>
> >>> Can't you hi
* Suman Anna [150311 10:18]:
> On 03/11/2015 11:26 AM, Tony Lindgren wrote:
> > * Dave Gerlach [150310 12:55]:
> >> Suman and I have been looking at this together, so I can comment here. An
> >> implementation like this is what Suman is referring to:
> >>
> >> + l4_wkup: l4_wkup@44c
On 11/03/15 17:19, Feng Kan wrote:
> On Wed, Mar 11, 2015 at 7:53 AM, Marc Zyngier wrote:
>> On 27/01/15 07:03, Pranavkumar Sawargaonkar wrote:
>>> In APM X-Gene, GIC register space is 64K aligned while the sizes mentioned
>>> in the dt are 4K aligned. This breaks KVM when kernel is built with 64K
On Wed, Mar 11, 2015 at 7:53 AM, Marc Zyngier wrote:
> On 27/01/15 07:03, Pranavkumar Sawargaonkar wrote:
>> In APM X-Gene, GIC register space is 64K aligned while the sizes mentioned
>> in the dt are 4K aligned. This breaks KVM when kernel is built with 64K page
>> size due to size alignment chec
Hi Tony,
On 03/11/2015 11:26 AM, Tony Lindgren wrote:
> * Dave Gerlach [150310 12:55]:
>> Tony,
>> On 03/10/2015 11:09 AM, Tony Lindgren wrote:
>>> * Suman Anna [150309 16:59]:
On 03/05/2015 10:57 AM, Tony Lindgren wrote:
> * Suman Anna [150305 08:47]:
>> On 03/05/2015 09:40 AM, To
Am 11.03.2015 um 17:44 schrieb Tony Lindgren :
> * Dr. H. Nikolaus Schaller [150311 09:17]:
>> Hi,
>>
>> Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
>>
>>> Hi,
>>>
>>> * Marek Belisko [150310 14:28]:
Signed-off-by: Marek Belisko
---
.../bindings/power_supply/twl4030_madc_b
Sascha Hauer writes:
> On Wed, Mar 11, 2015 at 11:16:31AM +0800, James Liao wrote:
>> Hi,
>>
>> On Tue, 2015-03-10 at 10:41 +0100, Sascha Hauer wrote:
>> > On Mon, Mar 09, 2015 at 02:35:03PM -0700, Kevin Hilman wrote:
>> > > Sascha Hauer writes:
>> > >
>> > > > Signed-off-by: Sascha Hauer
>>
* Dr. H. Nikolaus Schaller [150311 09:17]:
> Hi,
>
> Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
>
> > Hi,
> >
> > * Marek Belisko [150310 14:28]:
> >> Signed-off-by: Marek Belisko
> >> ---
> >> .../bindings/power_supply/twl4030_madc_battery.txt | 43
> >> ++
> >> 1 fil
Le 05/03/2015 08:35, Alexander Stein a écrit :
> This drivers allows a fixed framebuffer memory to be set by an additional
> IORESOURCE_MEM resource. Thus add an example to the DT documentation.
>
> Signed-off-by: Alexander Stein
> Acked-by: Nicolas Ferre
Queued in at91-4.1-dt. Thanks!
> ---
>
On 03/11/2015 11:59 AM, Rob Herring wrote:
On Wed, Mar 11, 2015 at 10:28 AM, Murali Karicheri wrote:
On 03/11/2015 08:49 AM, Russell King - ARM Linux wrote:
On Wed, Mar 11, 2015 at 07:35:45AM -0500, Rob Herring wrote:
On Tue, Mar 10, 2015 at 10:25 AM, Murali Karicheri
wrote:
On some platf
* Dave Gerlach [150310 12:55]:
> Tony,
> On 03/10/2015 11:09 AM, Tony Lindgren wrote:
> > * Suman Anna [150309 16:59]:
> >> On 03/05/2015 10:57 AM, Tony Lindgren wrote:
> >>> * Suman Anna [150305 08:47]:
> On 03/05/2015 09:40 AM, Tony Lindgren wrote:
> > * Dave Gerlach [150304 20:14]:
Hi,
Am 11.03.2015 um 16:24 schrieb Tony Lindgren :
> Hi,
>
> * Marek Belisko [150310 14:28]:
>> Signed-off-by: Marek Belisko
>> ---
>> .../bindings/power_supply/twl4030_madc_battery.txt | 43
>> ++
>> 1 file changed, 43 insertions(+)
>> create mode 100644
>> Documentation/
The early init code maps the kernel image using statically
allocated page tables. This means that we can only allow
Image to be placed such that we can map its entire static
footprint using a single table entry at all but the lowest
level. So update the documentation to reflect that the Image
shoul
Currently, the FDT blob needs to be in the same naturally aligned
512 MB region as the kernel, so that it can be mapped into the
kernel virtual memory space very early on using a minimal set of
statically allocated translation tables.
Now that we have early fixmap support, we can relax this restri
On Wed, Mar 11, 2015 at 10:28 AM, Murali Karicheri wrote:
> On 03/11/2015 08:49 AM, Russell King - ARM Linux wrote:
>>
>> On Wed, Mar 11, 2015 at 07:35:45AM -0500, Rob Herring wrote:
>>>
>>> On Tue, Mar 10, 2015 at 10:25 AM, Murali Karicheri
>>> wrote:
On some platforms such as that base
This series came about after Mark Rutland brought up the fact that the current
FDT placement logic used by the EFI stub is flawed. But actually, it turned out
that the documentation for both the Image and FDT placement was incorrect as
well, or confusing at the very least.
So this series does two
On Mar 11, 2015, at 10:33 AM, Bjorn Andersson wrote:
> On Tue, Mar 10, 2015 at 12:57 PM, Kumar Gala wrote:
>>
>> On Mar 10, 2015, at 2:52 PM, Arnd Bergmann wrote:
>>
>>> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
> The top level qcom,msm-id and qcom,board-id are utilized
On Tue, Mar 10, 2015 at 12:57 PM, Kumar Gala wrote:
>
> On Mar 10, 2015, at 2:52 PM, Arnd Bergmann wrote:
>
>> On Tuesday 10 March 2015 13:10:08 Kumar Gala wrote:
The top level qcom,msm-id and qcom,board-id are utilized by
bootloaders
> on Qualcomm MSM platf
On 03/11/2015 08:49 AM, Russell King - ARM Linux wrote:
On Wed, Mar 11, 2015 at 07:35:45AM -0500, Rob Herring wrote:
On Tue, Mar 10, 2015 at 10:25 AM, Murali Karicheri wrote:
On some platforms such as that based on x86, ia64 etc, root bus is
created with parent node passed in as NULL to pci_cr
On 03/11/2015 08:35 AM, Rob Herring wrote:
On Tue, Mar 10, 2015 at 10:25 AM, Murali Karicheri wrote:
On some platforms such as that based on x86, ia64 etc, root bus is
created with parent node passed in as NULL to pci_create_root_bus().
On these platforms, the patch series "PCI: get DMA configu
> On 07.03.2015, at 06:47, Stephen Warren wrote:
>
> These pins aren't used by anything on the board, but are rather part of
> the expansion header. I wonder if we wouldn't be better off removing any
> configuration of the pins from the DT. After all, we can't guarantee how
> the user has connect
* Eliad Peller [150311 06:39]:
> On Wed, Mar 11, 2015 at 3:21 PM, Javier Martinez Canillas
> wrote:
> > On Wed, Mar 11, 2015 at 2:17 PM, Arnd Bergmann wrote:
> >> On Wednesday 11 March 2015 14:07:11 Javier Martinez Canillas wrote:
> >>>
> >>> Right now it seems that all boards in mainline with a
On Wed, Mar 11, 2015 at 11:20:59AM +, Stathis Voukelatos wrote:
> Our feeling is that we will have to test and verify that a move to gPTP
> will fit with the use cases that we have to support and that will
> require a fair amount of effort and rewrite of application software.
> If the driver is
On 27/01/15 07:03, Pranavkumar Sawargaonkar wrote:
> In APM X-Gene, GIC register space is 64K aligned while the sizes mentioned
> in the dt are 4K aligned. This breaks KVM when kernel is built with 64K page
> size due to size alignment checking in vgic driver for VCPU Control and
> VCPU register.
>
Hi,
On 11-03-15 14:07, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 11 March 2015 06:33 PM, Hans de Goede wrote:
Hi,
On 11-03-15 13:50, Kishon Vijay Abraham I wrote:
Hi,
On Wednesday 11 March 2015 05:09 PM, Hans de Goede wrote:
Hi,
On 11-03-15 10:13, Kishon Vijay Abraham I wrote:
Hi,
Hi,
On 11-03-15 14:41, Maxime Ripard wrote:
On Tue, Mar 10, 2015 at 11:33:51PM +0100, Hans de Goede wrote:
and we have no way to replace U-Boot in NAND
so far (afaik). But replacing them by stdout-path is a very good
solution too.
You mean putting stdout-path in the dts, I'm not sure if I lik
On Wed, Mar 11, 2015 at 05:08:08PM +0800, Chen-Yu Tsai wrote:
> On Wed, Mar 11, 2015 at 4:52 PM, Maxime Ripard
> wrote:
> > On Wed, Mar 11, 2015 at 11:11:49AM +0800, Chen-Yu Tsai wrote:
> >> On Wed, Mar 11, 2015 at 5:32 AM, Maxime Ripard
> >> wrote:
> >> > On Tue, Mar 10, 2015 at 07:59:24PM +0800
Adds the i2c bus controller driver for the Ingenic JZ4780 SoC.
Signed-off-by: Zubair Lutfullah Kakakhel
---
V1 -> V2
Rebase to 4.0-rc3
Minor mistake fix in enable/disable functions
---
drivers/i2c/busses/Kconfig | 9 +
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-jz478
Hi,
Here we have two patches that add support for the i2c
controller present in the Ingenic JZ4780.
V1 - > V2
Rebased to v4.0-rc3
Minor tweaks/fixes. Details in individual patch commits.
Feedback welcome.
Thank-you
ZubairLK
Zubair Lutfullah Kakakhel (2):
dt-bindings: i2c: Add dt binding doc
On Tue, Mar 10, 2015 at 11:33:51PM +0100, Hans de Goede wrote:
> >>>and we have no way to replace U-Boot in NAND
> >>>so far (afaik). But replacing them by stdout-path is a very good
> >>>solution too.
> >>
> >>You mean putting stdout-path in the dts, I'm not sure if I like that,
> >>to me both boo
1 - 100 of 185 matches
Mail list logo
