* [PATCH 02/12] pinctrl: at91-pio4: account for const type of of_device_id.data
From: Linus Walleij @ 2018-01-03 7:58 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514899688-27844-3-git-send-email-Julia.Lawall@lip6.fr>
On Tue, Jan 2, 2018 at 2:27 PM, Julia Lawall <Julia.Lawall@lip6.fr> wrote:
> This driver creates a const structure that it stores in the data field
> of an of_device_id array.
>
> Adding const to the declaration of the location that receives the
> const value from the data field ensures that the compiler will
> continue to check that the value is not modified. Furthermore, the
> const-discarding cast on the extraction from the data field is no
> longer needed.
>
> Done using Coccinelle.
>
> Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Patch applied.
Yours,
Linus Walleij
^ permalink raw reply
* [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_
From: Geert Uytterhoeven @ 2018-01-03 7:49 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <87h8s3cvel.fsf@concordia.ellerman.id.au>
Hi Michael,
On Wed, Jan 3, 2018 at 7:24 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>
>> On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>>> Christoph Hellwig <hch@lst.de> writes:
>>>
>>>> We want to use the dma_direct_ namespace for a generic implementation,
>>>> so rename powerpc to the second best choice: dma_nommu_.
>>>
>>> I'm not a fan of "nommu". Some of the users of direct ops *are* using an
>>> IOMMU, they're just setting up a 1:1 mapping once at init time, rather
>>> than mapping dynamically.
>>>
>>> Though I don't have a good idea for a better name, maybe "1to1",
>>> "linear", "premapped" ?
>>
>> "identity"?
>
> I think that would be wrong, but thanks for trying to help :)
>
> The address on the device side is sometimes (often?) offset from the CPU
> address. So eg. the device can DMA to RAM address 0x0 using address
> 0x800000000000000.
>
> Identity would imply 0 == 0 etc.
>
> I think "bijective" is the correct term, but that's probably a bit
> esoteric.
OK, didn't know about the offset.
Then "linear" is what we tend to use, right?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* [PATCH 00/12] Marvell NAND controller rework with ->exec_op()
From: Miquel RAYNAL @ 2018-01-03 7:40 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <87d12scbiy.fsf@belgarion.home>
On Tue, 02 Jan 2018 20:21:09 +0100
Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> Miquel RAYNAL <miquel.raynal@free-electrons.com> writes:
>
> > I think the ECC issue you faced was related to pages being written
> > *and* empty. If this guess is right, the board should boot fine with
> > these changes.
> >
> > Otherwise, please add the DEBUG define as before in both the core
> > and the driver and do not hesitate to add another dump_stack()
> > where it crashes (if applicable).
>
> The problem looks still the same :
> [ 3.560163] Bad block table not found for chip 0
Mmmmh ok.
Can you please add this patch:
http://code.bulix.org/61at9p-254626
Thanks,
Miqu?l
>
> Cheers.
>
> --
> Robert
>
^ permalink raw reply
* [PATCH] nokia N9: Add support for magnetometer and touchscreen
From: Filip Matijević @ 2018-01-03 6:55 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180102172720.ghtez4d3d2fgcmj6@earth.universe>
Hi,
On 01/02/2018 06:27 PM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jan 02, 2018 at 02:17:22PM +0100, Pavel Machek wrote:
>> This adds dts support for magnetometer and touchscreen on Nokia N9.
>
> I think it makes sense to have this splitted.
>
>> Signed-off-by: Pavel Machek <pavel@ucw.cz>
>>
>> diff --git a/arch/arm/boot/dts/omap3-n9.dts b/arch/arm/boot/dts/omap3-n9.dts
>> index 39e35f8..57a6679 100644
>> --- a/arch/arm/boot/dts/omap3-n9.dts
>> +++ b/arch/arm/boot/dts/omap3-n9.dts
>> @@ -36,6 +57,22 @@
>> };
>> };
>> };
>> +
>> + touch at 4b {
>
> touchscreen@
>
>> + compatible = "atmel,maxtouch";
>> + reg = <0x4b>;
>> + interrupt-parent = <&gpio2>;
>> + interrupts = <29 2>; /* gpio_61, IRQF_TRIGGER_FALLING*/
>
> reset-gpios = <&gpio3 17 GPIO_ACTIVE_SOMETHING>;
>
I'm using reset-gpios = <&gpio3 17 0>;
>> + vdd-supply = <&vio>;
>> + avdd-supply = <&vaux1>;
>
> Those two are not mentioned in the binding and not supported by the
> driver as far as I can see?
>
Right, but vio and vaux1 need to be on - the reason why it's working at
all is because lis302 uses the same regulators and turns them on. IMHO
either we add the support for regulators to maxtouch driver or we add
regulator-always-on to vio and vaux1.
>> + };
>> +};
>
> Touchscreen with the same settings is required for n950, so it
> should be in the shared n950 + n9 file.
>
As a side-note, there is no pinmux mentioned and usually I'd use
OMAP3_CORE1_IOPAD(0x20c8, PIN_INPUT | MUX_MODE4) /* gpio_61*/
OMAP3_CORE1_IOPAD(0x20f2, PIN_OUTPUT | MUX_MODE4) /* gpio_81*/
For reasons that I can't explain, first line (gpmc_nbe1->gpio_61) breaks
it for me, so I've commented it out. Still, if anyone has an idea what
is wrong with that please let me know.
>> +&i2c3 {
>> + ak8975 at 0f {
>> + compatible = "asahi-kasei,ak8975";
>> + reg = <0x0f>;
>> + };
>> };
>
> Looking at the N9 board file this is missing a rotation matrix. This
> is supported by the binding:
>
> Documentation/devicetree/bindings/iio/magnetometer/ak8975.txt
>
>>
>> &isp {
>
> -- Sebastian
>
Best regards,
Filip
^ permalink raw reply
* [PATCH v2 4/4] dmaengine: xilinx_dma: Free BD consistent memory
From: Kedareswara rao Appana @ 2018-01-03 6:42 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514961731-1916-1-git-send-email-appanad@xilinx.com>
Free BD consistent memory while freeing the channel
i.e in free_chan_resources.
Signed-off-by: Radhey Shyam Pandey <radheys@xilinx.com>
Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
---
Changes for v2:
--> None.
drivers/dma/xilinx/xilinx_dma.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/dma/xilinx/xilinx_dma.c b/drivers/dma/xilinx/xilinx_dma.c
index 845e638..a9edbd8 100644
--- a/drivers/dma/xilinx/xilinx_dma.c
+++ b/drivers/dma/xilinx/xilinx_dma.c
@@ -764,6 +764,11 @@ static void xilinx_dma_free_chan_resources(struct dma_chan *dchan)
INIT_LIST_HEAD(&chan->free_seg_list);
spin_unlock_irqrestore(&chan->lock, flags);
+ /* Free memory that is allocated for BD */
+ dma_free_coherent(chan->dev, sizeof(*chan->seg_v) *
+ XILINX_DMA_NUM_DESCS, chan->seg_v,
+ chan->seg_p);
+
/* Free Memory that is allocated for cyclic DMA Mode */
dma_free_coherent(chan->dev, sizeof(*chan->cyclic_seg_v),
chan->cyclic_seg_v, chan->cyclic_seg_p);
--
2.7.4
^ permalink raw reply related
* [PATCH v2 3/4] dmaengine: xilinx_dma: Fix warning variable prev set but not used
From: Kedareswara rao Appana @ 2018-01-03 6:42 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514961731-1916-1-git-send-email-appanad@xilinx.com>
This patch fixes the below sparse warning in the driver
drivers/dma/xilinx/xilinx_dma.c: In function ?xilinx_vdma_dma_prep_interleaved?:
drivers/dma/xilinx/xilinx_dma.c:1614:43: warning: variable ?prev? set but not used [-Wunused-but-set-variable]
struct xilinx_vdma_tx_segment *segment, *prev = NULL;
Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
---
Changes for v2:
--> Improved commit message title and description
as suggested by Vinod.
drivers/dma/xilinx/xilinx_dma.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/dma/xilinx/xilinx_dma.c b/drivers/dma/xilinx/xilinx_dma.c
index 8467671..845e638 100644
--- a/drivers/dma/xilinx/xilinx_dma.c
+++ b/drivers/dma/xilinx/xilinx_dma.c
@@ -1611,7 +1611,7 @@ xilinx_vdma_dma_prep_interleaved(struct dma_chan *dchan,
{
struct xilinx_dma_chan *chan = to_xilinx_chan(dchan);
struct xilinx_dma_tx_descriptor *desc;
- struct xilinx_vdma_tx_segment *segment, *prev = NULL;
+ struct xilinx_vdma_tx_segment *segment;
struct xilinx_vdma_desc_hw *hw;
if (!is_slave_direction(xt->dir))
@@ -1665,8 +1665,6 @@ xilinx_vdma_dma_prep_interleaved(struct dma_chan *dchan,
/* Insert the segment into the descriptor segments list. */
list_add_tail(&segment->node, &desc->segments);
- prev = segment;
-
/* Link the last hardware descriptor with the first. */
segment = list_first_entry(&desc->segments,
struct xilinx_vdma_tx_segment, node);
--
2.7.4
^ permalink raw reply related
* [PATCH v2 2/4] dmaengine: xilinx_dma: properly configure the SG mode bit in the driver for cdma
From: Kedareswara rao Appana @ 2018-01-03 6:42 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514961731-1916-1-git-send-email-appanad@xilinx.com>
If the hardware is configured for Scatter Gather(SG) mode,
and hardware is idle, in the control register SG mode bit
must be set to a 0 then back to 1 by the software, to force
the CDMA SG engine to use a new value written to the CURDESC_PNTR
register, failure to do so could result errors from the dmaengine.
This patch updates the same.
Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
---
Changes for v2:
--> Improved commit message title and description
as suggested by Vinod.
drivers/dma/xilinx/xilinx_dma.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/dma/xilinx/xilinx_dma.c b/drivers/dma/xilinx/xilinx_dma.c
index 21ac954..8467671 100644
--- a/drivers/dma/xilinx/xilinx_dma.c
+++ b/drivers/dma/xilinx/xilinx_dma.c
@@ -1204,6 +1204,12 @@ static void xilinx_cdma_start_transfer(struct xilinx_dma_chan *chan)
}
if (chan->has_sg) {
+ dma_ctrl_clr(chan, XILINX_DMA_REG_DMACR,
+ XILINX_CDMA_CR_SGMODE);
+
+ dma_ctrl_set(chan, XILINX_DMA_REG_DMACR,
+ XILINX_CDMA_CR_SGMODE);
+
xilinx_write(chan, XILINX_DMA_REG_CURDESC,
head_desc->async_tx.phys);
@@ -2052,6 +2058,10 @@ static int xilinx_dma_terminate_all(struct dma_chan *dchan)
chan->cyclic = false;
}
+ if ((chan->xdev->dma_config->dmatype == XDMA_TYPE_CDMA) && chan->has_sg)
+ dma_ctrl_clr(chan, XILINX_DMA_REG_DMACR,
+ XILINX_CDMA_CR_SGMODE);
+
return 0;
}
--
2.7.4
^ permalink raw reply related
* [PATCH v2 1/4] dmaengine: xilinx_dma: populate dma caps properly
From: Kedareswara rao Appana @ 2018-01-03 6:42 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514961731-1916-1-git-send-email-appanad@xilinx.com>
When client driver uses dma_get_slave_caps() api,
it checks for certain fields of dma_device struct
currently driver is not settings the directions and addr_widths
fields resulting dma_get_slave_caps() returning failure.
This patch fixes this issue by populating proper values
to the struct dma_device directions and addr_widths fields.
Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
---
Changes for v2:
--> Improved commit message title and description
as suggested by Vinod.
drivers/dma/xilinx/xilinx_dma.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/dma/xilinx/xilinx_dma.c b/drivers/dma/xilinx/xilinx_dma.c
index 88d317d..21ac954 100644
--- a/drivers/dma/xilinx/xilinx_dma.c
+++ b/drivers/dma/xilinx/xilinx_dma.c
@@ -2398,6 +2398,7 @@ static int xilinx_dma_chan_probe(struct xilinx_dma_device *xdev,
chan->direction = DMA_MEM_TO_DEV;
chan->id = chan_id;
chan->tdest = chan_id;
+ xdev->common.directions = BIT(DMA_MEM_TO_DEV);
chan->ctrl_offset = XILINX_DMA_MM2S_CTRL_OFFSET;
if (xdev->dma_config->dmatype == XDMA_TYPE_VDMA) {
@@ -2415,6 +2416,7 @@ static int xilinx_dma_chan_probe(struct xilinx_dma_device *xdev,
chan->direction = DMA_DEV_TO_MEM;
chan->id = chan_id;
chan->tdest = chan_id - xdev->nr_channels;
+ xdev->common.directions |= BIT(DMA_DEV_TO_MEM);
chan->ctrl_offset = XILINX_DMA_S2MM_CTRL_OFFSET;
if (xdev->dma_config->dmatype == XDMA_TYPE_VDMA) {
@@ -2629,6 +2631,8 @@ static int xilinx_dma_probe(struct platform_device *pdev)
dma_cap_set(DMA_PRIVATE, xdev->common.cap_mask);
}
+ xdev->common.dst_addr_widths = BIT(addr_width / 8);
+ xdev->common.src_addr_widths = BIT(addr_width / 8);
xdev->common.device_alloc_chan_resources =
xilinx_dma_alloc_chan_resources;
xdev->common.device_free_chan_resources =
--
2.7.4
^ permalink raw reply related
* [PATCH v2 0/4] dmaengine: xilinx_dma: Bug fixes
From: Kedareswara rao Appana @ 2018-01-03 6:42 UTC (permalink / raw)
To: linux-arm-kernel
This patch series does the below
--> Fixes sparse warnings in the driver.
--> properly configures the SG mode bit in the driver for cdma.
--> populates dma caps properly.
This patch series got created on top of linux tag 4.15-rc4
i.e slave-dma.git next branch
Kedareswara rao Appana (4):
dmaengine: xilinx_dma: populate dma caps properly
dmaengine: xilinx_dma: properly configure the SG mode bit in the
driver for cdma
dmaengine: xilinx_dma: Fix warning variable prev set but not used
dmaengine: xilinx_dma: Free BD consistent memory
drivers/dma/xilinx/xilinx_dma.c | 23 ++++++++++++++++++++---
1 file changed, 20 insertions(+), 3 deletions(-)
--
2.7.4
^ permalink raw reply
* [PATCH v5 2/2] PCI: mediatek: Set up class type and vendor ID for MT7622
From: Honghui Zhang @ 2018-01-03 6:39 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180102105659.GB10536@red-moon>
On Tue, 2018-01-02 at 10:56 +0000, Lorenzo Pieralisi wrote:
> On Thu, Dec 28, 2017 at 09:39:12AM +0800, Honghui Zhang wrote:
> > On Wed, 2017-12-27 at 12:45 -0600, Bjorn Helgaas wrote:
> > > On Wed, Dec 27, 2017 at 08:59:54AM +0800, honghui.zhang at mediatek.com wrote:
> > > > From: Honghui Zhang <honghui.zhang@mediatek.com>
> > > >
> > > > + /* Set up class code for MT7622 */
> > > > + val = PCI_CLASS_BRIDGE_PCI << 16;
> > > > + writel(val, port->base + PCIE_CONF_CLASS);
> > >
> > > 1) Your comments mention MT7622 specifically, but this code is run for
> > > both mt2712-pcie and mt7622-pcie. If this code is safe and necessary
> > > for both mt2712-pcie and mt7622-pcie, please remove the mention of
> > > MT7622.
> >
> > Hmm, the code snippet added here will only be executed by MT7622, since
> > MT2712 will not enter this "if (pcie->base) {" condition.
> > Should the mention of MT7622 must be removed in this case?
>
> You should add an explicit way (eg of_device_is_compatible() match for
> instance) to apply the quirk just on the platform that requires it.
>
> Checking for "if (pcie->base)" is really not the way to do it.
>
hi, Lorenzo,
Thanks very much for your advise.
Passing the compatible string or platform data into this function needed
to add some new field in the struct mtk_pcie_port, then I guess both set
it for MT2712 and MT7622 is an easy way, since re-setting those values
for MT2712 is safe.
> > > 2) The first comment mentions both "vendor ID and device ID" but you
> > > don't write the device ID. Since this code applies to both
> > > mt2712-pcie and mt7622-pcie, my guess is that you don't *want* to
> > > write the device ID. If that's the case, please fix the comment.
> > >
> >
> > My bad, I did not check the comments carefully.
> > Thanks.
> >
> > > 3) If you only need to set the vendor ID, you're performing a 32-bit
> > > write (writel()) to update a 16-bit value. Please use writew()
> > > instead.
> > >
> >
> > Ok, thanks, I guess I could use the following code snippet in the next
> > version:
> > val = readl(port->base + PCIE_CONF_VENDOR_ID)
> > val &= ~GENMASK(15, 0);
> > val |= PCI_VENDOR_ID_MEDIATEK;
> > writel(val, port->base + PCIE_CONF_VENDOR_ID);
>
> Have you read Bjorn's comment ? Or there is a problem with using
> a writew() ?
>
This control register is a 32bit register, I'm not sure whether the apb
bus support write an 16bit value with 16bit but not 32bit address
alignment. I prefer the more safety old way of writel.
I need to do more test about the writew if the code elegant is more
important.
thanks.
> Lorenzo
>
> > > 4) If you only need to set the vendor ID, please use a definition like
> > > "PCIE_CONF_VENDOR_ID" instead of the ambiguous "PCIE_CONF_ID".
> > >
> > > 5) If you only need to set the vendor ID, please update the changelog
> > > to mention "vendor ID" specifically instead of the ambiguous "IDs".
> >
> > > 6) Please add a space before the closing "*/" of the first comment.
> > >
> > > 7) PCI_CLASS_BRIDGE_PCI is for a PCI-to-PCI bridge, i.e., one that has
> > > PCI on both the primary (upstream) side and the secondary (downstream)
> > > side. That kind of bridge has a type 1 config header (see
> > > PCI_HEADER_TYPE) and the PCI_PRIMARY_BUS and PCI_SECONDARY_BUS
> > > registers tell us the bus number of the primary and secondary sides.
> > >
> > > I don't believe this device is a PCI-to-PCI bridge. I think it's a
> > > *host* bridge that has some non-PCI interface on the upstream side and
> > > should have a type 0 config header. If that's the case you should use
> > > PCI_CLASS_BRIDGE_HOST instead.
> > >
> >
> > Thanks very much for your help with the review, I will fix the other
> > issue in the next version.
> >
> > > > }
> > > >
> > > > /* Assert all reset signals */
> > > > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > > > index ab20dc5..2480b0e 100644
> > > > --- a/include/linux/pci_ids.h
> > > > +++ b/include/linux/pci_ids.h
> > > > @@ -2113,6 +2113,8 @@
> > > >
> > > > #define PCI_VENDOR_ID_MYRICOM 0x14c1
> > > >
> > > > +#define PCI_VENDOR_ID_MEDIATEK 0x14c3
> > > > +
> > > > #define PCI_VENDOR_ID_TITAN 0x14D2
> > > > #define PCI_DEVICE_ID_TITAN_010L 0x8001
> > > > #define PCI_DEVICE_ID_TITAN_100L 0x8010
> > > > --
> > > > 2.6.4
> > > >
> >
> >
^ permalink raw reply
* [PATCH] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174
From: Ganapatrao Kulkarni @ 2018-01-03 6:32 UTC (permalink / raw)
To: linux-arm-kernel
When an interrupt is moved across node collections on ThunderX2
multi Socket platform, an interrupt stops routed to new collection
and results in loss of interrupts.
Adding workaround to issue INV after MOVI for cross-node collection
move to flush out the cached entry.
Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
---
Documentation/arm64/silicon-errata.txt | 1 +
arch/arm64/Kconfig | 11 +++++++++++
drivers/irqchip/irq-gic-v3-its.c | 24 ++++++++++++++++++++++++
3 files changed, 36 insertions(+)
diff --git a/Documentation/arm64/silicon-errata.txt b/Documentation/arm64/silicon-errata.txt
index fc1c884..fb27cb5 100644
--- a/Documentation/arm64/silicon-errata.txt
+++ b/Documentation/arm64/silicon-errata.txt
@@ -63,6 +63,7 @@ stable kernels.
| Cavium | ThunderX Core | #27456 | CAVIUM_ERRATUM_27456 |
| Cavium | ThunderX Core | #30115 | CAVIUM_ERRATUM_30115 |
| Cavium | ThunderX SMMUv2 | #27704 | N/A |
+| Cavium | ThunderX2 ITS | #174 | CAVIUM_ERRATUM_174 |
| Cavium | ThunderX2 SMMUv3| #74 | N/A |
| Cavium | ThunderX2 SMMUv3| #126 | N/A |
| | | | |
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index c9a7e9e..71a7e30 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -461,6 +461,17 @@ config ARM64_ERRATUM_843419
If unsure, say Y.
+config CAVIUM_ERRATUM_174
+ bool "Cavium ThunderX2 erratum 174"
+ depends on NUMA
+ default y
+ help
+ LPI stops routed to redistributors after inter node collection
+ move in ITS. Enable workaround to invalidate ITS entry after
+ inter-node collection move.
+
+ If unsure, say Y.
+
config CAVIUM_ERRATUM_22375
bool "Cavium erratum 22375, 24313"
default y
diff --git a/drivers/irqchip/irq-gic-v3-its.c b/drivers/irqchip/irq-gic-v3-its.c
index 06f025f..d8b9c96 100644
--- a/drivers/irqchip/irq-gic-v3-its.c
+++ b/drivers/irqchip/irq-gic-v3-its.c
@@ -46,6 +46,7 @@
#define ITS_FLAGS_CMDQ_NEEDS_FLUSHING (1ULL << 0)
#define ITS_FLAGS_WORKAROUND_CAVIUM_22375 (1ULL << 1)
#define ITS_FLAGS_WORKAROUND_CAVIUM_23144 (1ULL << 2)
+#define ITS_FLAGS_WORKAROUND_CAVIUM_174 (1ULL << 3)
#define RDIST_FLAGS_PROPBASE_NEEDS_FLUSHING (1 << 0)
@@ -1119,6 +1120,12 @@ static int its_set_affinity(struct irq_data *d, const struct cpumask *mask_val,
if (cpu != its_dev->event_map.col_map[id]) {
target_col = &its_dev->its->collections[cpu];
its_send_movi(its_dev, target_col, id);
+ if (its_dev->its->flags & ITS_FLAGS_WORKAROUND_CAVIUM_174) {
+ /* Issue INV for cross node collection move. */
+ if (cpu_to_node(cpu) !=
+ cpu_to_node(its_dev->event_map.col_map[id]))
+ its_send_inv(its_dev, id);
+ }
its_dev->event_map.col_map[id] = cpu;
irq_data_update_effective_affinity(d, cpumask_of(cpu));
}
@@ -2904,6 +2911,15 @@ static int its_force_quiescent(void __iomem *base)
}
}
+static bool __maybe_unused its_enable_quirk_cavium_174(void *data)
+{
+ struct its_node *its = data;
+
+ its->flags |= ITS_FLAGS_WORKAROUND_CAVIUM_174;
+
+ return true;
+}
+
static bool __maybe_unused its_enable_quirk_cavium_22375(void *data)
{
struct its_node *its = data;
@@ -3031,6 +3047,14 @@ static const struct gic_quirk its_quirks[] = {
.init = its_enable_quirk_hip07_161600802,
},
#endif
+#ifdef CONFIG_CAVIUM_ERRATUM_174
+ {
+ .desc = "ITS: Cavium ThunderX2 erratum 174",
+ .iidr = 0x13f, /* ThunderX2 pass A1/A2/B0 */
+ .mask = 0xffffffff,
+ .init = its_enable_quirk_cavium_174,
+ },
+#endif
{
}
};
--
2.9.4
^ permalink raw reply related
* [PATCH] ARM: dts: sun8i: a83t: bananapi-m3: Add LED device nodes
From: Chen-Yu Tsai @ 2018-01-03 6:28 UTC (permalink / raw)
To: linux-arm-kernel
The Bananapi M3 has two controllable LEDs, blue and green, that are tied
to the PMIC's two GPIO pins.
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
---
arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts b/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts
index 6550bf0e594b..78fe61d97790 100644
--- a/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts
+++ b/arch/arm/boot/dts/sun8i-a83t-bananapi-m3.dts
@@ -60,6 +60,20 @@
stdout-path = "serial0:115200n8";
};
+ leds {
+ compatible = "gpio-leds";
+
+ blue {
+ label = "bananapi-m3:blue:usr";
+ gpios = <&axp_gpio 1 GPIO_ACTIVE_HIGH>;
+ };
+
+ green {
+ label = "bananapi-m3:green:usr";
+ gpios = <&axp_gpio 0 GPIO_ACTIVE_HIGH>;
+ };
+ };
+
reg_usb1_vbus: reg-usb1-vbus {
compatible = "regulator-fixed";
regulator-name = "usb1-vbus";
--
2.15.1
^ permalink raw reply related
* [PATCH 16/67] powerpc: rename dma_direct_ to dma_nommu_
From: Michael Ellerman @ 2018-01-03 6:24 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CAMuHMdWWus2kNSOzS94k-3678826W1YjKwCWTquu3hBLZ80cvw@mail.gmail.com>
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> On Tue, Jan 2, 2018 at 10:45 AM, Michael Ellerman <mpe@ellerman.id.au> wrote:
>> Christoph Hellwig <hch@lst.de> writes:
>>
>>> We want to use the dma_direct_ namespace for a generic implementation,
>>> so rename powerpc to the second best choice: dma_nommu_.
>>
>> I'm not a fan of "nommu". Some of the users of direct ops *are* using an
>> IOMMU, they're just setting up a 1:1 mapping once at init time, rather
>> than mapping dynamically.
>>
>> Though I don't have a good idea for a better name, maybe "1to1",
>> "linear", "premapped" ?
>
> "identity"?
I think that would be wrong, but thanks for trying to help :)
The address on the device side is sometimes (often?) offset from the CPU
address. So eg. the device can DMA to RAM address 0x0 using address
0x800000000000000.
Identity would imply 0 == 0 etc.
I think "bijective" is the correct term, but that's probably a bit
esoteric.
cheers
^ permalink raw reply
* [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning
From: Appana Durga Kedareswara Rao @ 2018-01-03 6:10 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180103052746.GI18649@localhost>
Hi Vinod,
>On Wed, Jan 03, 2018 at 05:13:29AM +0000, Appana Durga Kedareswara Rao
>wrote:
>> Hi Vinod,
>>
>> Thanks for the review...
>>
>> >
>> >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote:
>> >
>> >Fix title here too
>>
>> Sure will fix in v2...
>>
>> >
>> >BTW whats with LINUX tag in patches, pls drop them
>>
>> Ok will mention the Linux tag info in the cover letter patch from the
>> next patch series on wards...
>
>Please wrap your replies within 80chars. It is very hard to read! I have reflown for
>readability
Sure will take care of it next time onwards...
>
>Can you explain what you mean by that info, what are you trying to convey?
What I mean here is will mention the Linux kernel tag
Information in the cover letter patch...
Regards,
Kedar.
>
>--
>~Vinod
^ permalink raw reply
* [GIT PULL 5/5] i.MX defconfig updates for 4.16
From: Shawn Guo @ 2018-01-03 5:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514959040-9992-1-git-send-email-shawnguo@kernel.org>
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-defconfig-4.16
for you to fetch changes up to 189114b47b1cfcc5da02db9bcafebd2042aa7ab8:
ARM: imx_v6_v7_defconfig: enable CONFIG_CPU_FREQ_STAT (2017-12-26 17:04:13 +0800)
----------------------------------------------------------------
i.MX defconfig updates for 4.16:
- Enable CPU_FREQ_STAT for cpufreq transtion statistics support.
- Enable SRTC driver RTC_DRV_MXC_V2 for i.MX53.
- Turn on a few drivers useful for DART-MX6 SoM support, SERDEV
bluetooth, SERIAL_DEV_BUS, WL18XX, and DEFAULT_ON LED Trigger.
----------------------------------------------------------------
Dong Aisheng (1):
ARM: imx_v6_v7_defconfig: enable CONFIG_CPU_FREQ_STAT
Neil Armstrong (1):
ARM: imx_v6_v7_defconfig: Add missing config for DART-MX6 SoM
Patrick Bruenn (1):
ARM: imx_v6_v7_defconfig: enable RTC_DRV_MXC_V2
arch/arm/configs/imx_v6_v7_defconfig | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
^ permalink raw reply
* [GIT PULL 4/5] Freescale arm64 device tree updates for 4.16
From: Shawn Guo @ 2018-01-03 5:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514959040-9992-1-git-send-email-shawnguo@kernel.org>
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt64-4.16
for you to fetch changes up to 1e33300782235ae6fdc891d9c3ba04ba59da6f3d:
arm64: dts: ls208xa: add power monitor chip node (2017-12-26 17:14:13 +0800)
----------------------------------------------------------------
Freescale arm64 device tree updates for 4.16:
- LS1088A updates: add device support for DCFG, qoriq-mc, and USB.
- Add power monitor device INA220 for ls208xa-rdb board.
----------------------------------------------------------------
Ashish Kumar (1):
arm64: dts: ls1088a: Added dcfg node in ls1088a dtsi
Ioana Ciornei (1):
arm64: dts: ls1088a: add fsl-mc hardware resource manager node
Yuantian Tang (1):
arm64: dts: ls208xa: add power monitor chip node
yinbo.zhu (1):
arm64: dts: ls1088a: Add USB support
arch/arm64/boot/dts/freescale/fsl-ls1088a-rdb.dts | 8 ++
arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 97 ++++++++++++++++++++++
arch/arm64/boot/dts/freescale/fsl-ls208xa-rdb.dtsi | 12 +++
3 files changed, 117 insertions(+)
^ permalink raw reply
* [GIT PULL 3/5] i.MX device tree updates for 4.16
From: Shawn Guo @ 2018-01-03 5:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514959040-9992-1-git-send-email-shawnguo@kernel.org>
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt-4.16
for you to fetch changes up to 84a82ef70e1eb2a7a90bc19eed27cb27a8e4c54c:
ARM: dts: imx7s: Avoid using label in unit address and reg (2017-12-27 10:52:39 +0800)
----------------------------------------------------------------
i.MX device tree changes for 4.16:
- A few random updates for vf610-zii board: correct switch EEPROM size,
enable edma1, correct GPIO expander interrupt, add PHYs for switch2
device.
- LS1021A device tree updates: add reboot and QSPI device nodes, label
USB controllers, specify interrupt-affinity for PMU, fix TMR_FIPER1
setting, enable esdhc device, add Moxa UC-8410A board support.
- A bunch of patches from Fabio: fix reg - unit address mismatches,
remove leading zero in unit address, move regulators out of
simple-bus, move nodes with no reg property out of bus, remove extra
clock cell, add missing phy-cells to usb-nop-xceiv, etc.
- A couple series from Hummingboard developers: re-organise device tree
files for better handling various board versions, and then add the
new hummingboard2 board support on top of that.
- Disable AC'97 input pins pad and add support for powering off for
imx6qdl-udoo board.
- Convert from fbdev to drm bindings for imx6sx-sdb and imx6sl-evk
board.
- Add device tree for Variscite DART-MX6 SoM and Carrier-board support.
- Add new board support of TS-4600 and TS-7970 from Technologic
Systems.
- A series from Stefan to update imx7-colibri device tree and then add
new version of Toradex Colibri iMX7D board with eMMC support.
- Other random updates on various board support.
----------------------------------------------------------------
Andrew Lunn (1):
ARM: dts: vf610-zii-dev-c: Fix switch EEPROM size
Esben Haabendal (2):
ARM: dts: ls1021a: Add label to USB controllers
ARM: dts: ls1021a: Specify interrupt-affinity for pmu node
Fabio Estevam (41):
ARM: dts: imx6qdl-wandboard-revd1: Make EDID functional
ARM: dts: imx6sx: Fix the PCI representation
ARM: dts: imx6sx-sdb: Rearrange the regulators node
ARM: dts: imx6sx-sdb: Add PCIe support
ARM: dts: imx6qdl-sabreauto: Pass the DDC I2C bus
ARM: dts: imx6qdl-sabreauto: Add CEC support
ARM: dts: imx53-cx9020: Fix the Ethernet PHY reset GPIO polarity
ARM: dts: imx53: Move nodes which have no reg property out of bus
ARM: dts: imx6: Move nodes which have no reg property out of bus
ARM: dts: imx6: Add unit address and reg for the anatop nodes
ARM: dts: imx6dl: Pass the reg properties for mipi nodes
ARM: dts: imx6dl: Remove unneeded label and unit address
ARM: dts: imx7: Move nodes which have no reg property out of bus
ARM: dts: imx7d: Fix pcie node warnings
ARM: dts: imx7s: Add unit address and reg for the anatop nodes
ARM: dts: vfxxx: Move nodes which have no reg property out of bus
ARM: dts: imx6sx: Fix spba-bus unit address
ARM: dts: vf500: Fix interrupt-controller unit address
ARM: dts: imx51-ts4800: Fix syscon and touschscreen nodes
ARM: dts: imx51-zii-rdu1: Add the unit addresses in sysled
ARM: dts: imx53-m53: Remove unneeded reg property
ARM: dts: imx53-tx53-x03x: Move display node out of 'soc'
ARM: dts: imx6qdl-apf6dev: Move regulators out of simple-bus
ARM: dts: imx6qdl-aristainetos: Move regulators out of simple-bus
ARM: dts: imx6qdl-aristainetos: Move display node out of 'soc'
ARM: dts: imx6qdl-apalis: Remove unneeded reg property
ARM: dts: imx6qdl-colibri: Remove unneeded reg property
ARM: dts: imx6q-h100: Remove unneeded unit address
ARM: dts: imx6qdl-nitrogen6_max: Remove unneeded unit address
ARM: dts: imx6ul-14x14-evk: Move regulators out of simple-bus
ARM: dts: imx6qdl-zii-rdu2: Remove device_type from PCI subnode
ARM: dts: imx51-babbage: Pass the USB PHY regulator
ARM: dts: imx6sx: Fix PCI non-prefetchable memory range
ARM: dts: imx6sx: Add support for PCI power domain
dt-bindings: imx-gpcv2: Fix the unit address
ARM: dts: ls1021a-qds: Remove extra clock cell
ARM: dts: ls1021a-twr: Remove extra clock cell
ARM: dts: imx51-babbage: Fix the 26MHz clock modelling
ARM: dts: imx6qdl-hummingboard2: Remove leading zero in unit address
ARM: dts: imx51-zii-rdu1: Add missing #phy-cells to usb-nop-xceiv
ARM: dts: imx7s: Avoid using label in unit address and reg
Jon Nettleton (1):
ARM: dts: imx6qdl: add HummingBoard2 boards
Lucas Stach (10):
ARM: dts: imx6: RDU2: add i210 node
ARM: dts: imx: rdu1: cosmetic changes to the audio nodes
ARM: dts: imx6: RDU2: add alias for RTC
ARM: dts: imx6*-hummingboard2: fix formatting
ARM: dts: imx6*-hummingboard2: add SGTL5000 VDDD supply
ARM: dts: imx6*-hummingboard2: remove LDB node
ARM: dts: imx6*-hummingboard2: fix PCIe reset polarity
ARM: dts: imx6*-hummingboard2: remove non-mainline property from RTC
ARM: dts: imx6*-hummingboard2: remove redundant PWM disables
ARM: dts: imx6*-hummingboard2: rework regulators
Maciej S. Szmigiero (2):
ARM: dts: imx6qdl-udoo: disable AC'97 input pins pad drivers
ARM: dts: imx6qdl-udoo: add support for powering off
Marco Franchi (4):
ARM: dts: imx53-tx53: Fix 'ethernet-phy at 0' node with unit name and no reg property
ARM: dts: imx6sx-sdb: Convert from fbdev to drm bindings
ARM: dts: imx6sl-evk: Rearrange the regulators node
ARM: dts: imx6sl-evk: Convert from fbdev to drm bindings
Mathieu Malaterre (1):
ARM: imx: dts: Use lower case for bindings notation
Michael Tretter (1):
ARM: dts: imx6q-h100: use usdhc2 VSELECT
Neil Armstrong (5):
ARM: dts: imx6qdl-pinfunc: Add missing MX6QDL_PAD_ENET_RXD0__OSC32K_32K_OUT
dt-bindings: Add vendor prefix for Solomon Goldentek Display Corporation
dt-bindings: display: Add bindings for SGD GKTW70SDAE4SE Panel
ARM: dts: imx6qdl: Add Variscite DART-MX6 SoM support
ARM: dts: imx6q: Add Variscite DART-MX6 Carrier-board support
Oleksij Rempel (1):
ARM: dts: imx6: add snvs-lpgpr node
Otavio Salvador (1):
ARM: dts: imx6qdl-nitrogen6x: Add SPI NOR partitions
Patrick Bruenn (1):
ARM: dts: imx53: add srtc node
Prabhakar Kushwaha (1):
ARM: dts: ls1021aqds: Add nand node for ifc controller
Rasmus Villemoes (2):
ARM: dts: ls1021a: add "fsl,ls1021a-esdhc" compatible string to esdhc node
ARM: dts: ls1021a: add reboot node to .dtsi
Rob Herring (1):
ARM: dts: imx: Add missing #phy-cells to usb-nop-xceiv
Russell King (31):
ARM: dts: imx6qdl: SolidRun: remove redundant regulators node
ARM: dts: imx6qdl: SolidRun: move AR8035 into microsom
ARM: dts: imx6qdl-microsom: rename to imx6qdl-sr-som
ARM: dts: imx6qdl: SolidRun: move microsom includes into .dts
ARM: dts: imx6qdl-sr-som: use real iomuxc values for ethernet
ARM: dts: imx6qdl-sr-som: split out Broadcom Wi-Fi support
ARM: dts: imx6qdl-sr-som-brcm: rename sdio clock
ARM: dts: imx6qdl-sr-som: add 3.3V vcc regulator
ARM: dts: imx6qdl-sr-som: add support for TI Wi-Fi
ARM: dts: imx6qdl-sr-som: add support for eMMC
ARM: dts: imx6qdl-hummingboard: add SD card regulator
ARM: dts: imx6qdl: SolidRun: rename regulators to match schematic
ARM: dts: imx6qdl: SolidRun: fix node names
ARM: dts: imx6qdl: SolidRun: add v1.5 som without eMMC
ARM: dts: imx6qdl: SolidRun: add v1.5 som with eMMC
ARM: dts: imx6qdl-cubox-i: update GPIO specification
ARM: dts: imx6*-hummingboard2: remove ar8035 include
ARM: dts: imx6qdl-hummingboard2: rename microsom include
ARM: dts: imx6*-hummingboard2: move microsom includes into .dts
ARM: dts: imx6*-hummingboard2: add Broadcom Wi-Fi include
ARM: dts: imx6*-hummingboard2: fix SD card detect
ARM: dts: imx6*-hummingboard2: use proper gpio flags definitions
ARM: dts: imx6*-hummingboard2: convert to more conventional vmmc-supply
ARM: dts: imx6*-hummingboard2: split out eMMC support
ARM: dts: imx6qdl-hummingboard2: add PWM3 support
ARM: dts: imx6qdl-hummingboard2: add v1.5 som without eMMC
ARM: dts: imx6qdl-hummingboard2: add v1.5 som with eMMC
ARM: dts: imx6qdl-hummingboard2: rename regulators to match schematic
ARM: dts: vf610-zii-dev: enable edma1
ARM: dts: vf610-zii-dev-rev-b: fix interrupt for GPIO expander
ARM: dts: vf610-zii-dev-rev-b: add PHYs for switch2
SZ Lin (2):
ARM: dts: ls1021a: Add support for QSPI with ls1021a SoC
ARM: dts: ls1021a: add support for Moxa UC-8410A open platform
Sebastien Bourdelin (4):
of: documentation: add bindings documentation for TS-7970
ARM: dts: TS-7970: add basic device tree
of: documentation: add bindings documentation for TS-4600
ARM: dts: TS-4600: add basic device tree
Stefan Agner (10):
ARM: dts: colibri/apalis: use correct compatible for RTC
ARM: dts: imx7-colibri: move and rename USB Host power regulator
ARM: dts: imx7-colibri: make sure multiplexed pins are not active
ARM: dts: imx7-colibri: mux pull-ups where appropriate
ARM: dts: imx7-colibri: use NAND_CE1 as GPIO
ARM: dts: imx7-colibri: specify cpu-supply
ARM: dts: imx7-colibri: specify usdhc1 supplies
ARM: dts: imx7-colibri: specify backlight GPIO
ARM: dts: imx7-colibri: add MCP2515 CAN controller
ARM: dts: imx7: add Toradex Colibri iMX7D 1GB (eMMC) support
Troy Kisky (1):
ARM: dts: imx: name the interrupts for the fec ethernet driver
Vanessa Maegima (1):
ARM: dts: imx7d-pico-pi: Separate into cpu and baseboard dts
Yangbo Lu (1):
ARM: dts: ls1021a: fix the value of TMR_FIPER1
yinbo.zhu (1):
ARM: dts: ls1021a: Enable the esdhc
.../devicetree/bindings/arm/technologic.txt | 11 +
.../bindings/display/panel/sgd,gktw70sdae4se.txt | 41 ++
.../devicetree/bindings/power/fsl,imx-gpcv2.txt | 4 +-
.../devicetree/bindings/vendor-prefixes.txt | 1 +
arch/arm/boot/dts/Makefile | 22 +-
arch/arm/boot/dts/imx25.dtsi | 2 +
arch/arm/boot/dts/imx27-pdk.dts | 1 +
arch/arm/boot/dts/imx27-phytec-phycore-rdk.dts | 1 +
arch/arm/boot/dts/imx27-phytec-phycore-som.dtsi | 1 +
arch/arm/boot/dts/imx28-ts4600.dts | 79 +++
arch/arm/boot/dts/imx35.dtsi | 2 +
arch/arm/boot/dts/imx51-babbage.dts | 77 ++-
.../boot/dts/imx51-eukrea-mbimxsd51-baseboard.dts | 1 +
arch/arm/boot/dts/imx51-ts4800.dts | 6 +-
arch/arm/boot/dts/imx51-zii-rdu1.dts | 12 +-
arch/arm/boot/dts/imx51.dtsi | 1 +
arch/arm/boot/dts/imx53-cx9020.dts | 2 +-
arch/arm/boot/dts/imx53-m53.dtsi | 1 -
arch/arm/boot/dts/imx53-tx53-x03x.dts | 232 ++++----
arch/arm/boot/dts/imx53-tx53.dtsi | 14 +-
arch/arm/boot/dts/imx53.dtsi | 48 +-
arch/arm/boot/dts/imx6dl-aristainetos_4.dts | 50 +-
arch/arm/boot/dts/imx6dl-aristainetos_7.dts | 48 +-
arch/arm/boot/dts/imx6dl-colibri-eval-v3.dts | 2 +-
arch/arm/boot/dts/imx6dl-cubox-i-emmc-som-v15.dts | 52 ++
arch/arm/boot/dts/imx6dl-cubox-i-som-v15.dts | 51 ++
arch/arm/boot/dts/imx6dl-cubox-i.dts | 2 +
.../boot/dts/imx6dl-hummingboard-emmc-som-v15.dts | 53 ++
arch/arm/boot/dts/imx6dl-hummingboard-som-v15.dts | 52 ++
arch/arm/boot/dts/imx6dl-hummingboard.dts | 2 +
.../boot/dts/imx6dl-hummingboard2-emmc-som-v15.dts | 55 ++
arch/arm/boot/dts/imx6dl-hummingboard2-som-v15.dts | 54 ++
arch/arm/boot/dts/imx6dl-hummingboard2.dts | 53 ++
arch/arm/boot/dts/imx6dl-pinfunc.h | 1 +
arch/arm/boot/dts/imx6dl-ts7970.dts | 50 ++
arch/arm/boot/dts/imx6dl.dtsi | 12 +-
arch/arm/boot/dts/imx6q-apalis-eval.dts | 2 +-
arch/arm/boot/dts/imx6q-apalis-ixora-v1.1.dts | 2 +-
arch/arm/boot/dts/imx6q-apalis-ixora.dts | 2 +-
arch/arm/boot/dts/imx6q-cubox-i-emmc-som-v15.dts | 60 +++
arch/arm/boot/dts/imx6q-cubox-i-som-v15.dts | 59 ++
arch/arm/boot/dts/imx6q-cubox-i.dts | 2 +
arch/arm/boot/dts/imx6q-display5.dtsi | 2 +-
arch/arm/boot/dts/imx6q-h100.dts | 33 +-
.../boot/dts/imx6q-hummingboard-emmc-som-v15.dts | 61 +++
arch/arm/boot/dts/imx6q-hummingboard-som-v15.dts | 60 +++
arch/arm/boot/dts/imx6q-hummingboard.dts | 2 +
.../boot/dts/imx6q-hummingboard2-emmc-som-v15.dts | 63 +++
arch/arm/boot/dts/imx6q-hummingboard2-som-v15.dts | 62 +++
arch/arm/boot/dts/imx6q-hummingboard2.dts | 61 +++
arch/arm/boot/dts/imx6q-pinfunc.h | 1 +
arch/arm/boot/dts/imx6q-ts7970.dts | 54 ++
arch/arm/boot/dts/imx6q-var-dt6customboard.dts | 235 ++++++++
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 1 -
arch/arm/boot/dts/imx6qdl-apf6dev.dtsi | 44 +-
arch/arm/boot/dts/imx6qdl-aristainetos.dtsi | 73 ++-
arch/arm/boot/dts/imx6qdl-aristainetos2.dtsi | 76 ++-
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 1 -
arch/arm/boot/dts/imx6qdl-cubox-i.dtsi | 72 +--
arch/arm/boot/dts/imx6qdl-hummingboard.dtsi | 103 ++--
arch/arm/boot/dts/imx6qdl-hummingboard2-emmc.dtsi | 72 +++
arch/arm/boot/dts/imx6qdl-hummingboard2.dtsi | 540 +++++++++++++++++++
arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 10 +-
arch/arm/boot/dts/imx6qdl-nitrogen6x.dtsi | 17 +
arch/arm/boot/dts/imx6qdl-sabreauto.dtsi | 9 +
...6qdl-microsom.dtsi => imx6qdl-sr-som-brcm.dtsi} | 41 +-
arch/arm/boot/dts/imx6qdl-sr-som-emmc.dtsi | 70 +++
arch/arm/boot/dts/imx6qdl-sr-som-ti.dtsi | 170 ++++++
...dl-microsom-ar8035.dtsi => imx6qdl-sr-som.dtsi} | 36 +-
arch/arm/boot/dts/imx6qdl-ts7970.dtsi | 594 +++++++++++++++++++++
arch/arm/boot/dts/imx6qdl-udoo.dtsi | 25 +-
arch/arm/boot/dts/imx6qdl-var-dart.dtsi | 503 +++++++++++++++++
arch/arm/boot/dts/imx6qdl-wandboard-revd1.dtsi | 5 +
arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi | 14 +-
arch/arm/boot/dts/imx6qdl.dtsi | 161 +++---
arch/arm/boot/dts/imx6sl-evk.dts | 133 +++--
arch/arm/boot/dts/imx6sl.dtsi | 48 +-
arch/arm/boot/dts/imx6sx-sdb.dtsi | 220 ++++----
arch/arm/boot/dts/imx6sx.dtsi | 93 ++--
arch/arm/boot/dts/imx6ul-14x14-evk.dts | 19 +-
arch/arm/boot/dts/imx6ul.dtsi | 49 +-
arch/arm/boot/dts/imx7-colibri-eval-v3.dtsi | 39 +-
arch/arm/boot/dts/imx7-colibri.dtsi | 116 +++-
arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts | 19 +
arch/arm/boot/dts/imx7d-colibri-emmc.dtsi | 21 +
arch/arm/boot/dts/imx7d-colibri-eval-v3.dts | 13 +-
arch/arm/boot/dts/imx7d-colibri.dtsi | 4 +
arch/arm/boot/dts/imx7d-pico-pi.dts | 181 +++++++
.../boot/dts/{imx7d-pico.dts => imx7d-pico.dtsi} | 133 -----
arch/arm/boot/dts/imx7d.dtsi | 22 +-
arch/arm/boot/dts/imx7s.dtsi | 133 ++---
arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts | 241 +++++++++
arch/arm/boot/dts/ls1021a-qds.dts | 7 +-
arch/arm/boot/dts/ls1021a-twr.dts | 6 +-
arch/arm/boot/dts/ls1021a.dtsi | 30 +-
arch/arm/boot/dts/vf-colibri-eval-v3.dtsi | 2 +-
arch/arm/boot/dts/vf500.dtsi | 2 +-
arch/arm/boot/dts/vf610-zii-dev-rev-b.dts | 20 +-
arch/arm/boot/dts/vf610-zii-dev-rev-c.dts | 4 +-
arch/arm/boot/dts/vf610-zii-dev.dtsi | 4 +
arch/arm/boot/dts/vfxxx.dtsi | 10 +-
101 files changed, 5005 insertions(+), 1058 deletions(-)
create mode 100644 Documentation/devicetree/bindings/display/panel/sgd,gktw70sdae4se.txt
create mode 100644 arch/arm/boot/dts/imx28-ts4600.dts
create mode 100644 arch/arm/boot/dts/imx6dl-cubox-i-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-cubox-i-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-hummingboard-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-hummingboard-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-hummingboard2-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-hummingboard2-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6dl-hummingboard2.dts
create mode 100644 arch/arm/boot/dts/imx6dl-ts7970.dts
create mode 100644 arch/arm/boot/dts/imx6q-cubox-i-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-cubox-i-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-hummingboard-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-hummingboard-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-hummingboard2-emmc-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-hummingboard2-som-v15.dts
create mode 100644 arch/arm/boot/dts/imx6q-hummingboard2.dts
create mode 100644 arch/arm/boot/dts/imx6q-ts7970.dts
create mode 100644 arch/arm/boot/dts/imx6q-var-dt6customboard.dts
create mode 100644 arch/arm/boot/dts/imx6qdl-hummingboard2-emmc.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-hummingboard2.dtsi
rename arch/arm/boot/dts/{imx6qdl-microsom.dtsi => imx6qdl-sr-som-brcm.dtsi} (85%)
create mode 100644 arch/arm/boot/dts/imx6qdl-sr-som-emmc.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-sr-som-ti.dtsi
rename arch/arm/boot/dts/{imx6qdl-microsom-ar8035.dtsi => imx6qdl-sr-som.dtsi} (84%)
create mode 100644 arch/arm/boot/dts/imx6qdl-ts7970.dtsi
create mode 100644 arch/arm/boot/dts/imx6qdl-var-dart.dtsi
create mode 100644 arch/arm/boot/dts/imx7d-colibri-emmc-eval-v3.dts
create mode 100644 arch/arm/boot/dts/imx7d-colibri-emmc.dtsi
create mode 100644 arch/arm/boot/dts/imx7d-pico-pi.dts
rename arch/arm/boot/dts/{imx7d-pico.dts => imx7d-pico.dtsi} (71%)
create mode 100644 arch/arm/boot/dts/ls1021a-moxa-uc-8410a.dts
^ permalink raw reply
* [GIT PULL 2/5] i.MX SoC updates for 4.16
From: Shawn Guo @ 2018-01-03 5:57 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <1514959040-9992-1-git-send-email-shawnguo@kernel.org>
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-soc-4.16
for you to fetch changes up to 5b2576ecf19418de699e230587a6d0b928a05e31:
ARM: imx: remove unused imx3 pm definitions (2017-12-26 16:30:20 +0800)
----------------------------------------------------------------
i.MX SoC updates for 4.16:
- Drop power saving status checking from MMDC driver probe function,
since there is nothing really depending on power saving being
enabled.
- Clean up unused imx3 pm definitions.
----------------------------------------------------------------
Lucas Stach (1):
ARM: imx: don't abort MMDC probe if power saving status doesn't match
Martin Kaiser (1):
ARM: imx: remove unused imx3 pm definitions
arch/arm/mach-imx/common.h | 9 ---------
arch/arm/mach-imx/mmdc.c | 11 -----------
2 files changed, 20 deletions(-)
^ permalink raw reply
* [GIT PULL 1/5] i.MX drivers updates for 4.16
From: Shawn Guo @ 2018-01-03 5:57 UTC (permalink / raw)
To: linux-arm-kernel
The following changes since commit 50c4c4e268a2d7a3e58ebb698ac74da0de40ae36:
Linux 4.15-rc3 (2017-12-10 17:56:26 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-drivers-4.16
for you to fetch changes up to cfabb7921ccbede2968e5049d433ba3d0e0950af:
soc: imx: gpc: Add i.MX6SX PCI power domain (2017-12-26 16:26:46 +0800)
----------------------------------------------------------------
i.MX drivers update for 4.16:
- Update i.MX GPC driver to support PCI power domain of i.MX6SX SoC.
----------------------------------------------------------------
Fabio Estevam (1):
soc: imx: gpc: Add i.MX6SX PCI power domain
Documentation/devicetree/bindings/power/fsl,imx-gpc.txt | 3 +++
drivers/soc/imx/gpc.c | 16 +++++++++++++++-
2 files changed, 18 insertions(+), 1 deletion(-)
^ permalink raw reply
* [PATCH 02/11] clk: sunxi-ng: a83t: Add M divider to TCON1 clock
From: Chen-Yu Tsai @ 2018-01-03 5:46 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20171230210203.24115-3-jernej.skrabec@siol.net>
On Sun, Dec 31, 2017 at 5:01 AM, Jernej Skrabec <jernej.skrabec@siol.net> wrote:
> TCON1 also has M divider, contrary to TCON0.
>
> Fixes: 05359be1176b ("clk: sunxi-ng: Add driver for A83T CCU")
>
> Signed-off-by: Jernej Skrabec <jernej.skrabec@siol.net>
Added "And the mux is only 2 bits wide, instead of 3." to the commit
message and applied.
ChenYu
^ permalink raw reply
* [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning
From: Vinod Koul @ 2018-01-03 5:27 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <CY1PR02MB169249D209C6E76AA7067269DC1E0@CY1PR02MB1692.namprd02.prod.outlook.com>
On Wed, Jan 03, 2018 at 05:13:29AM +0000, Appana Durga Kedareswara Rao wrote:
> Hi Vinod,
>
> Thanks for the review...
>
> >
> >On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote:
> >
> >Fix title here too
>
> Sure will fix in v2...
>
> >
> >BTW whats with LINUX tag in patches, pls drop them
>
> Ok will mention the Linux tag info in the cover letter patch from the next
> patch series on wards...
Please wrap your replies within 80chars. It is very hard to read! I have
reflown for readability
Can you explain what you mean by that info, what are you trying to convey?
--
~Vinod
^ permalink raw reply
* [LINUX PATCH 3/4] dmaengine: xilinx_dma: Fix compilation warning
From: Appana Durga Kedareswara Rao @ 2018-01-03 5:13 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180103035918.GH18649@localhost>
Hi Vinod,
Thanks for the review...
>
>On Thu, Dec 21, 2017 at 03:41:37PM +0530, Kedareswara rao Appana wrote:
>
>Fix title here too
Sure will fix in v2...
>
>BTW whats with LINUX tag in patches, pls drop them
Ok will mention the Linux tag info in the cover letter patch from the next patch series on wards...
Regards,
Kedar.
>
>> This patch fixes the below sparse warning in the driver
>> drivers/dma/xilinx/xilinx_dma.c: In function
>?xilinx_vdma_dma_prep_interleaved?:
>> drivers/dma/xilinx/xilinx_dma.c:1614:43: warning: variable ?prev? set but not
>used [-Wunused-but-set-variable]
>> struct xilinx_vdma_tx_segment *segment, *prev = NULL;
>>
>> Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
>> ---
>> drivers/dma/xilinx/xilinx_dma.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/dma/xilinx/xilinx_dma.c
>> b/drivers/dma/xilinx/xilinx_dma.c index 8467671..845e638 100644
>> --- a/drivers/dma/xilinx/xilinx_dma.c
>> +++ b/drivers/dma/xilinx/xilinx_dma.c
>> @@ -1611,7 +1611,7 @@ xilinx_vdma_dma_prep_interleaved(struct dma_chan
>> *dchan, {
>> struct xilinx_dma_chan *chan = to_xilinx_chan(dchan);
>> struct xilinx_dma_tx_descriptor *desc;
>> - struct xilinx_vdma_tx_segment *segment, *prev = NULL;
>> + struct xilinx_vdma_tx_segment *segment;
>> struct xilinx_vdma_desc_hw *hw;
>>
>> if (!is_slave_direction(xt->dir))
>> @@ -1665,8 +1665,6 @@ xilinx_vdma_dma_prep_interleaved(struct dma_chan
>*dchan,
>> /* Insert the segment into the descriptor segments list. */
>> list_add_tail(&segment->node, &desc->segments);
>>
>> - prev = segment;
>> -
>> /* Link the last hardware descriptor with the first. */
>> segment = list_first_entry(&desc->segments,
>> struct xilinx_vdma_tx_segment, node);
>> --
>> 2.7.4
>>
>
>--
>~Vinod
^ permalink raw reply
* [LINUX PATCH 2/4] dmaengine: xilinx_dma: Fix race condition in the driver for cdma
From: Appana Durga Kedareswara Rao @ 2018-01-03 5:10 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180103035845.GG18649@localhost>
Hi Vinod,
Thanks for the review...
>
>On Thu, Dec 21, 2017 at 03:41:36PM +0530, Kedareswara rao Appana wrote:
>
>same issue for patch title here too
Ok will fix in v2...
>
>> when hardware is idle we need to toggle the SG bit in the control
>> register, inorder to update new value to the current descriptor
>> register other wise undefined results will occur.
>
>can you try making it bit more clear..
Sure will fix in v2...
Regards,
Kedar.
>
>>
>> This patch updates the same.
>>
>> Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
>> ---
>> drivers/dma/xilinx/xilinx_dma.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/drivers/dma/xilinx/xilinx_dma.c
>> b/drivers/dma/xilinx/xilinx_dma.c index 21ac954..8467671 100644
>> --- a/drivers/dma/xilinx/xilinx_dma.c
>> +++ b/drivers/dma/xilinx/xilinx_dma.c
>> @@ -1204,6 +1204,12 @@ static void xilinx_cdma_start_transfer(struct
>xilinx_dma_chan *chan)
>> }
>>
>> if (chan->has_sg) {
>> + dma_ctrl_clr(chan, XILINX_DMA_REG_DMACR,
>> + XILINX_CDMA_CR_SGMODE);
>> +
>> + dma_ctrl_set(chan, XILINX_DMA_REG_DMACR,
>> + XILINX_CDMA_CR_SGMODE);
>> +
>> xilinx_write(chan, XILINX_DMA_REG_CURDESC,
>> head_desc->async_tx.phys);
>>
>> @@ -2052,6 +2058,10 @@ static int xilinx_dma_terminate_all(struct dma_chan
>*dchan)
>> chan->cyclic = false;
>> }
>>
>> + if ((chan->xdev->dma_config->dmatype == XDMA_TYPE_CDMA) &&
>chan->has_sg)
>> + dma_ctrl_clr(chan, XILINX_DMA_REG_DMACR,
>> + XILINX_CDMA_CR_SGMODE);
>> +
>> return 0;
>> }
>>
>> --
>> 2.7.4
>>
>
>--
>~Vinod
^ permalink raw reply
* [LINUX PATCH 1/4] dmaengine: xilinx_dma: Fix dma_get_slave_caps() API failures
From: Appana Durga Kedareswara Rao @ 2018-01-03 5:09 UTC (permalink / raw)
To: linux-arm-kernel
In-Reply-To: <20180103035735.GF18649@localhost>
Hi Vinod,
Thanks for the review...
>
>On Thu, Dec 21, 2017 at 03:41:35PM +0530, Kedareswara rao Appana wrote:
>
>Patch title should say what is does, not the cause/effect
Sure will fix in v2...
>
>An apt title might be "populate dma caps properly"
>
>> When client driver uses dma_get_slave_caps() api, it checks for
>> certain fields of dma_device struct currently driver is not settings
>> few fields resulting
>> dma_get_slave_caps() returning failure.
>
>It would help to mention the fields you are setting here
Sure will fix in v2...
Regards,
Kedar.
>
>>
>> This patch fixes this issue by populating proper values to the struct
>> dma_device fields.
>>
>> Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
>> ---
>> drivers/dma/xilinx/xilinx_dma.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/dma/xilinx/xilinx_dma.c
>> b/drivers/dma/xilinx/xilinx_dma.c index 88d317d..21ac954 100644
>> --- a/drivers/dma/xilinx/xilinx_dma.c
>> +++ b/drivers/dma/xilinx/xilinx_dma.c
>> @@ -2398,6 +2398,7 @@ static int xilinx_dma_chan_probe(struct
>xilinx_dma_device *xdev,
>> chan->direction = DMA_MEM_TO_DEV;
>> chan->id = chan_id;
>> chan->tdest = chan_id;
>> + xdev->common.directions = BIT(DMA_MEM_TO_DEV);
>>
>> chan->ctrl_offset = XILINX_DMA_MM2S_CTRL_OFFSET;
>> if (xdev->dma_config->dmatype == XDMA_TYPE_VDMA) { @@ -
>2415,6
>> +2416,7 @@ static int xilinx_dma_chan_probe(struct xilinx_dma_device *xdev,
>> chan->direction = DMA_DEV_TO_MEM;
>> chan->id = chan_id;
>> chan->tdest = chan_id - xdev->nr_channels;
>> + xdev->common.directions |= BIT(DMA_DEV_TO_MEM);
>>
>> chan->ctrl_offset = XILINX_DMA_S2MM_CTRL_OFFSET;
>> if (xdev->dma_config->dmatype == XDMA_TYPE_VDMA) { @@ -
>2629,6
>> +2631,8 @@ static int xilinx_dma_probe(struct platform_device *pdev)
>> dma_cap_set(DMA_PRIVATE, xdev->common.cap_mask);
>> }
>>
>> + xdev->common.dst_addr_widths = BIT(addr_width / 8);
>> + xdev->common.src_addr_widths = BIT(addr_width / 8);
>> xdev->common.device_alloc_chan_resources =
>> xilinx_dma_alloc_chan_resources;
>> xdev->common.device_free_chan_resources =
>> --
>> 2.7.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe dmaengine"
>> in the body of a message to majordomo at vger.kernel.org More majordomo
>> info at http://vger.kernel.org/majordomo-info.html
>
>--
>~Vinod
^ permalink raw reply
* [GIT PULL] ARM: aspeed: dts changes for 4.16
From: Joel Stanley @ 2018-01-03 4:17 UTC (permalink / raw)
To: linux-arm-kernel
Hello ARM maintainers,
Here are the ASPEED devicetree updates for 4.16.
They've had a run through a few next trees where Stephen noticed two minor
merge conflicts[1] that should be obvious to resolve, but please let me know if
you have concerns.
[1] https://lkml.org/lkml/2017/12/21/750
As discussed with Arnd, there is a commit for a clock header in
include/dt-bindings
that is also being merged through the clk tree. This should require no special
attention.
Thanks!
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
tags/aspeed-4.16-devicetree
for you to fetch changes up to e40ed274489a5f516da120186578eb379b452ac6:
ARM: dts: aspeed-evb: Add unit name to memory node (2017-12-21 14:03:22 +1030)
----------------------------------------------------------------
ASPEED device tree updates for 4.16
Clock driver support:
Rework all platforms to use proper clock bindings. Linux should now boot
upstream kernels on ast2400 and ast2500 platforms without out of tree
patches.
New systems:
Witherspoon: OpenPower Power9 server manufactured by IBM that uses
the ASPEED ast2500
Zaius: OpenPower Power9 server manufactured by Invatech that uses the
ASPEED ast2500
Q71L: Intel Xeon server manufactured by Qanta that uses the ASPEED ast2400
We also see updates to the Palmetto and Romulus systems to bring them in
line with the functionality of those above.
The systems take advantage of recently added drivers for LPC Snoop
device and the PWM/Tachometer fan controller.
OpenBMC flash layout:
The flash layout used OpenBMC systems is added and the device trees now
use it.
----------------------------------------------------------------
Andrew Jeffery (1):
ARM: dts: aspeed: Add LPC and child devices
Joel Stanley (17):
dt-bindings: clock: Add ASPEED constants
dt-bindings: gpio: Add ASPEED constants
ARM: dts: aspeed: Add proper clock references
ARM: dts: aspeed: Add MAC clocks
ARM: dts: aspeed: Add watchdog clocks
ARM: dts: aspeed: Add flash controller clocks
ARM: dts: aspeed: Add clock phandle to GPIO
ARM: dts: aspeed: Add PWM and tachometer node
ARM: dts: aspeed: Add LPC Snoop device
ARM: dts: aspeed: Remove skeleton.dtsi
ARM: dts: aspeed: Update license headers
ARM: dts: Add OpenBMC flash layout
ARM: dts: aspeed: Sort ASPEED entries in makefile
ARM: dts: aspeed: Add Witherspoon BMC machine
ARM: dts: aspeed-romulus: Update Romulus system
ARM: dts: aspeed-plametto: Add flash layout and fix memory node
ARM: dts: aspeed-evb: Add unit name to memory node
Rick Altherr (1):
ARM: dts: aspeed: Add Qanta Q71L BMC machine
Xo Wang (1):
ARM: dts: aspeed: Add Ingrasys Zaius BMC machine
arch/arm/boot/dts/Makefile | 8 +-
arch/arm/boot/dts/aspeed-ast2500-evb.dts | 4 +-
arch/arm/boot/dts/aspeed-bmc-opp-palmetto.dts | 5 +-
arch/arm/boot/dts/aspeed-bmc-opp-romulus.dts | 135 +++++-
arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts | 548 +++++++++++++++++++++++
arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts | 426 ++++++++++++++++++
arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts | 458 +++++++++++++++++++
arch/arm/boot/dts/aspeed-g4.dtsi | 165 ++++---
arch/arm/boot/dts/aspeed-g5.dtsi | 156 ++++---
arch/arm/boot/dts/openbmc-flash-layout.dtsi | 32 ++
include/dt-bindings/clock/aspeed-clock.h | 52 +++
include/dt-bindings/gpio/aspeed-gpio.h | 49 ++
12 files changed, 1888 insertions(+), 150 deletions(-)
create mode 100644 arch/arm/boot/dts/aspeed-bmc-opp-witherspoon.dts
create mode 100644 arch/arm/boot/dts/aspeed-bmc-opp-zaius.dts
create mode 100644 arch/arm/boot/dts/aspeed-bmc-quanta-q71l.dts
create mode 100644 arch/arm/boot/dts/openbmc-flash-layout.dtsi
create mode 100644 include/dt-bindings/clock/aspeed-clock.h
create mode 100644 include/dt-bindings/gpio/aspeed-gpio.h
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox