Re: [PATCH V5 3/3] PCI: Mask and unmask hotplug interrupts during reset

2018-07-03 Thread okaya
On 2018-07-03 06:52, p...@codeaurora.org wrote: On 2018-07-03 14:04, Lukas Wunner wrote: On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote: If a bridge supports hotplug and observes a PCIe fatal error, the following events happen: 1. AER driver removes the devices from PCI tree on

Re: [PATCH V5 3/3] PCI: Mask and unmask hotplug interrupts during reset

2018-07-03 Thread okaya
On 2018-07-03 04:34, Lukas Wunner wrote: On Mon, Jul 02, 2018 at 06:52:47PM -0400, Sinan Kaya wrote: If a bridge supports hotplug and observes a PCIe fatal error, the following events happen: 1. AER driver removes the devices from PCI tree on fatal error 2. AER driver brings down the link by

Re: [PATCH V4 7/7] PCI: Handle link reset via hotplug if supported

2018-07-01 Thread okaya
On 2018-07-01 13:14, Lukas Wunner wrote: On Thu, Jun 28, 2018 at 03:31:05PM -0400, Sinan Kaya wrote: +static pci_ers_result_t pciehp_reset_link(struct pci_dev *pdev) +{ + struct pcie_device *pciedev; + struct controller *ctrl; + struct device *devhp; + struct slot *slot;

Re: ACPI support in common clock framework

2018-06-14 Thread okaya
On 2018-06-14 06:58, Srinath Mannam wrote: Thank you Andy, Regards, Srinath. On Wed, Jun 13, 2018 at 1:43 PM, Andy Shevchenko wrote: +Cc: Rafael, ACPI ML On Wed, Jun 13, 2018 at 7:14 AM, Srinath Mannam wrote: Hi Michael, Stephen, We are adding ACPI support in our Linux based platform. At

Re: Requirement to get BAR pci_bus_address in user space

2018-06-14 Thread okaya
On 2018-06-14 06:29, Srinath Mannam wrote: ++ Alex Williamson, kvm, Hi Christoph, Thank you for quick reply. If we want to add this in vfio then I think we need to do the same in uio case also. As I mentioned in previous mail, in the current implementation resource information (address and

Re: [PATCH] staging: rts5208: add check on NULL before dereference

2018-06-09 Thread okaya
On 2018-06-09 15:34, Andy Shevchenko wrote: On Sat, Jun 9, 2018 at 7:58 PM, wrote: On 2018-06-09 12:38, Anton Vasilyev wrote: If rtsx_probe fails to allocate dev->chip, then NULL pointer dereference occurs at rtsx_release_resources(). Patch adds checks chip on NULL before its dereference

Re: [PATCH] staging: rts5208: add check on NULL before dereference

2018-06-09 Thread okaya
On 2018-06-09 12:38, Anton Vasilyev wrote: If rtsx_probe fails to allocate dev->chip, then NULL pointer dereference occurs at rtsx_release_resources(). Patch adds checks chip on NULL before its dereference at rtsx_release_resources and passing with dereference inside rtsx_release_chip. Found

Re: [PATCH NEXT 6/6] PCI/PORTDRV: Remove ERR_FATAL handling from pcie_portdrv_slot_reset()

2018-06-08 Thread okaya
On 2018-06-08 00:57, p...@codeaurora.org wrote: On 2018-06-08 03:04, Bjorn Helgaas wrote: On Thu, Jun 07, 2018 at 07:18:03PM +0530, p...@codeaurora.org wrote: On 2018-06-07 11:30, Oza Pawandeep wrote: > We are handling ERR_FATAL by resetting the Link in software,skipping the > driver

Re: [PATCH V4] PCI: move early dump functionality from x86 arch into the common code

2018-06-05 Thread okaya
On 2018-06-05 05:12, Andy Shevchenko wrote: On Tue, Jun 5, 2018 at 5:16 AM, Sinan Kaya wrote: Move early dump functionality into common code so that it is available for all archtiectures. No need to carry arch specific reads around as the read hooks are already initialized by the time

Re: [PATCH V2] PCI/portdrv: do not disable device on reboot/shutdown

2018-05-25 Thread okaya
On 2018-05-25 15:10, Bjorn Helgaas wrote: On Fri, May 25, 2018 at 09:30:59AM -0400, Sinan Kaya wrote: On 5/24/2018 2:35 PM, Bjorn Helgaas wrote: > That sounds like a reasonable idea, and it is definitely another can > of worms. I looked briefly at some of the .shutdown() cases: should we

Re: [PATCH V2] PCI/portdrv: do not disable device on reboot/shutdown

2018-05-24 Thread okaya
On 2018-05-24 09:07, Bjorn Helgaas wrote: On Thu, May 24, 2018 at 07:43:05AM -0400, Sinan Kaya wrote: On 5/23/2018 6:57 PM, Sinan Kaya wrote: >> The crash seems to indicate that the hpsa device attempted a DMA after >> we cleared the Root Port's PCI_COMMAND_MASTER, which means >>

Re: [PATCH v15 3/9] PCI/AER: Handle ERR_FATAL with removal and re-enumeration of devices

2018-05-10 Thread okaya
On 2018-05-10 14:10, Bjorn Helgaas wrote: On Thu, May 10, 2018 at 12:31:16PM +0530, p...@codeaurora.org wrote: On 2018-05-10 04:51, Bjorn Helgaas wrote: > On Wed, May 09, 2018 at 06:44:53PM +0530, p...@codeaurora.org wrote: > > On 2018-05-09 18:37, Bjorn Helgaas wrote: > > > On Tue, May 08,

Re: [PATCH] pci/aspm: Remove CONFIG_PCIEASPM_DEBUG

2018-05-09 Thread okaya
On 2018-05-09 00:01, Rajat Jain wrote: Currently, the linux kernel disables ASPM when a device is removed from the kernel. But it is not enabled again when a new device is added on that slot even if it was originally enabled (by the BIOS) when the system booted up (assuming POLICY_DEFAULT).

Re: [PATCH] PCI: pciehp: Add quirk for QDF2400 Command Completed erratum

2018-05-07 Thread okaya
On 2018-05-07 22:35, Bjorn Helgaas wrote: On Sun, May 06, 2018 at 06:30:53AM -0400, Sinan Kaya wrote: The QDF2400 controller does not set the Command Completed bit unless writes to the Slot Command register change "Control" bits. Command Completed is never set for writes that only change

Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago)

2018-05-04 Thread okaya
On 2018-05-04 14:33, Bjorn Helgaas wrote: On Fri, May 04, 2018 at 07:37:40AM +0100, ok...@codeaurora.org wrote: On 2018-05-04 03:45, Bjorn Helgaas wrote: > On Thu, May 03, 2018 at 10:49:24AM +0200, Paul Menzel wrote: > > On 04/27/18 21:22, Bjorn Helgaas wrote: > > > [+cc Lukas, Sinan] > > > > >

Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago)

2018-05-04 Thread okaya
On 2018-05-04 03:45, Bjorn Helgaas wrote: On Thu, May 03, 2018 at 10:49:24AM +0200, Paul Menzel wrote: On 04/27/18 21:22, Bjorn Helgaas wrote: > [+cc Lukas, Sinan] > On Thu, Apr 26, 2018 at 12:17:53PM +0200, Paul Menzel wrote: > > On the Lenovo X60t, during resume from ACPI suspend and during

Re: pciehp 0000:00:1c.0:pcie004: Timeout on hotplug command 0x1038 (issued 65284 msec ago)

2018-04-28 Thread okaya
On 2018-04-27 21:18, Dave Young wrote: On 04/28/18 at 08:56am, Dave Young wrote: On 04/27/18 at 04:12pm, Bjorn Helgaas wrote: > [+cc Eric, Vivek, kexec list] > > On Fri, Apr 27, 2018 at 03:34:30PM -0400, Sinan Kaya wrote: > > On 4/27/2018 3:22 PM, Bjorn Helgaas wrote: > > > Sinan mooted the

Re: [PATCH] dmaengine: dmatest: Remove use of VLAs

2018-04-09 Thread okaya
On 2018-04-09 19:14, Laura Abbott wrote: On 04/09/2018 03:48 PM, Sinan Kaya wrote: On 4/9/2018 5:06 PM, Laura Abbott wrote: + /* dst_cnt can't be more than u8 */ + dma_addr_t dma_pq[255]; This is 2k stack space on 64 bit architectures. Isn't that a

Re: [PATCH v4 1/5] io: define several IO & PIO barrier types for the asm-generic version

2018-04-06 Thread okaya
On 2018-04-06 06:19, Arnd Bergmann wrote: On Thu, Apr 5, 2018 at 3:09 PM, Sinan Kaya wrote: Getting ready to harden readX()/writeX() and inX()/outX() semantics for the generic implementation. Defining two set of macros as __io_br() and __io_ar() to indicate actions to

Re: [PATCH v3 1/5] io: define several IO & PIO barrier types for the asm-generic version

2018-04-05 Thread okaya
On 2018-04-05 03:00, Arnd Bergmann wrote: On Thu, Apr 5, 2018 at 1:58 AM, Sinan Kaya wrote: Looks good, but I'd change the comments to ones that document exactly what those barriers are for: +#ifndef __io_ar +#ifdef rmb +/* prefer rmb() as the default implementation of

Re: [PATCH v1] PCI/DPC: Rename from pcie-dpc.c to dpc.c.

2018-03-31 Thread okaya
On 2018-03-31 18:34, Bjorn Helgaas wrote: From: Bjorn Helgaas Rename from pcie-dpc.c to dpc.c. The path "drivers/pci/pcie/pcie-dpc.c" has more occurrences of "pci" than necessary. Makes perfect sense. Signed-off-by: Bjorn Helgaas ---

Re: [PATCH v4 17/17] net: ena: Eliminate duplicate barriers on weakly-ordered archs

2018-03-25 Thread okaya
On 2018-03-25 08:06, Belgazal, Netanel wrote: I think you should either add a parameter to ena_com_write_sq_doorbell() or add ena_com_write_sq_doorbell_rel(). Right now, you have unused function. That is true. I got rid of ena_com_write_sq_doorbell_rel. On 3/20/18, 4:43 AM, "Sinan Kaya"

Re: [PATCH v4 4/6] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

2018-03-22 Thread okaya
On 2018-03-22 08:24, ok...@codeaurora.org wrote: On 2018-03-22 02:44, kbuild test robot wrote: Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6 next-20180321] [if your patch is applied to the wrong git

Re: [PATCH v4 4/6] infiniband: cxgb4: Eliminate duplicate barriers on weakly-ordered archs

2018-03-22 Thread okaya
On 2018-03-22 02:44, kbuild test robot wrote: Hi Sinan, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc6 next-20180321] [if your patch is applied to the wrong git tree, please drop us a note to help improve the

Re: [PATCH v4 12/17] net: cxgb4/cxgb4vf: Eliminate duplicate barriers on weakly-ordered archs

2018-03-21 Thread okaya
On 2018-03-21 19:03, Casey Leedom wrote: [[ Appologies for the DUPLICATE email. I forgot to tell my Mail Agent to use Plain Text. -- Casey ]] I feel very uncomfortable with these proposed changes. Our team is right in the middle of trying to tease our way through the various platform

Re: [PATCH REPOST v4 5/7] ixgbevf: keep writel() closer to wmb()

2018-03-21 Thread okaya
On 2018-03-21 17:54, David Miller wrote: From: Jeff Kirsher Date: Wed, 21 Mar 2018 14:48:08 -0700 On Wed, 2018-03-21 at 14:56 -0400, Sinan Kaya wrote: Remove ixgbevf_write_tail() in favor of moving writel() close to wmb(). Signed-off-by: Sinan Kaya

Re: [PATCH REPOST v4 5/7] ixgbevf: keep writel() closer to wmb()

2018-03-21 Thread okaya
On 2018-03-21 17:48, Jeff Kirsher wrote: On Wed, 2018-03-21 at 14:56 -0400, Sinan Kaya wrote: Remove ixgbevf_write_tail() in favor of moving writel() close to wmb(). Signed-off-by: Sinan Kaya Reviewed-by: Alexander Duyck ---

Re: [PATCH v4 3/7] scsi: dpt_i2o: eliminate duplicate barriers on weakly-ordered archs

2018-03-20 Thread okaya
On 2018-03-20 06:23, Christoph Hellwig wrote: This is a basically unmaintained driver for historic hardware, and not the right place for micro-optimizations. Sure, I can drop this on the next version.

Re: [PATCH 7/7] ixgbevf: eliminate duplicate barriers on weakly-ordered archs

2018-03-14 Thread okaya
On 2018-03-14 01:08, Timur Tabi wrote: On 3/13/18 10:20 PM, Sinan Kaya wrote: +/* Assumes caller has executed a write barrier to order memory and device + * requests. + */ static inline void ixgbevf_write_tail(struct ixgbevf_ring *ring, u32 value) { - writel(value, ring->tail); +

Re: [PATCH 3/7] RDMA/qedr: eliminate duplicate barriers on weakly-ordered archs

2018-03-14 Thread okaya
On 2018-03-14 00:12, Jason Gunthorpe wrote: On Tue, Mar 13, 2018 at 11:20:24PM -0400, Sinan Kaya wrote: Code includes wmb() followed by writel() in multiple places. writel() already has a barrier on some architectures like arm64. This ends up CPU observing two barriers back to back before

Re: [PATCH] ACPI/PCI: pci_link: reduce verbosity when IRQ is enabled

2018-02-04 Thread okaya
On 2018-02-04 04:03, Rafael J. Wysocki wrote: On Thu, Feb 1, 2018 at 8:32 AM, Rafael J. Wysocki wrote: On Mon, Jan 29, 2018 at 8:01 PM, Sinan Kaya wrote: Rafael, On 1/16/2018 4:49 PM, Bjorn Helgaas wrote: On Tue, Jan 16, 2018 at 01:53:00PM -0500,

Re: [PATCH] nvme: Acknowledge completion queue on each iteration

2017-07-17 Thread okaya
On 2017-07-17 18:56, Keith Busch wrote: On Mon, Jul 17, 2017 at 06:46:11PM -0400, Sinan Kaya wrote: Hi Keith, On 7/17/2017 6:45 PM, Keith Busch wrote: > On Mon, Jul 17, 2017 at 06:36:23PM -0400, Sinan Kaya wrote: >> Code is moving the completion queue doorbell after processing all completed >>

Re: [RFC 1/8] Introduce Peer-to-Peer memory (p2pmem) device

2017-03-31 Thread okaya
On 2017-03-31 21:57, Logan Gunthorpe wrote: On 31/03/17 05:51 PM, Sinan Kaya wrote: You can put a restriction with DMI/SMBIOS such that all devices from 2016 work else they belong to blacklist. How do you get a manufacturing date for a given device within the kernel? Is this actually

Re: [PATCH V2] PCI/ASPM: reconfigure ASPM following hotplug for POLICY_DEFAULT

2017-03-03 Thread okaya
On 2017-03-03 04:43, Patel, Mayurkumar wrote: Hi Kaya Hi Mayurkumar On 3/2/2017 11:05 AM, Patel, Mayurkumar wrote: Hi Bjorn, On 2/28/2017 1:57 PM, Patel, Mayurkumar wrote: I was trying to figure out when to use saved values vs. the values in registers by looking at the enable_cnt.

Re: [PATCH 2/2] iommu: add warning when sharing groups

2017-02-14 Thread okaya
On 2017-02-14 18:51, Alex Williamson wrote: On Tue, 14 Feb 2017 16:25:22 -0500 Sinan Kaya wrote: The ACS requirement has been obscured in the current code and is only known by certain individuals who happen to read the code. Print out a warning with ACS path failure when

Re: [PATCH] ACPI/IORT: Fix iort_node_get_id() mapping entries indexing

2017-01-09 Thread okaya
On 2017-01-09 01:34, Hanjun Guo wrote: Hi Sinan, On 2017/1/8 5:09, Sinan Kaya wrote: On 1/5/2017 1:29 PM, Lorenzo Pieralisi wrote: Commit 618f535a6062 ("ACPI/IORT: Add single mapping function") introduced a function (iort_node_get_id()) to retrieve ids for IORT named components.

Re: [PATCH V7 4/4] dmaengine: qcom_hidma: add MSI support for interrupts

2016-10-24 Thread okaya
On 2016-10-24 03:30, Andy Shevchenko wrote: On Mon, Oct 24, 2016 at 5:55 AM, Sinan Kaya wrote: On 10/21/2016 12:11 PM, Andy Shevchenko wrote: +static void hidma_free_msis(struct hidma_dev *dmadev) > +{ > +#ifdef CONFIG_GENERIC_MSI_IRQ_DOMAIN Perhaps one #ifdef and two

Re: Why MSI is limited to 32 interrupts maximum

2016-10-15 Thread okaya
On 2016-10-15 06:30, Bharat Kumar Gogada wrote: On Sat, 15 Oct 2016 12:37:55 + Bharat Kumar Gogada wrote: Hi Bharat, > Can anyone tell why MSI interrupts are limited to maximum 32 > interrupts, even though we have 16bit message data register ? That's the

Re: 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off

2016-09-30 Thread okaya
On 2016-09-30 02:44, Ondrej Zary wrote: On Friday 30 September 2016, Sinan Kaya wrote: On 9/29/2016 2:00 PM, Ondrej Zary wrote: >> The previous two patches were in the right direction. >> >> > Can we also get the same output from 4.6 kernel with the attached >> > patch for the same machine you

Re: 4.7 regression: ACPI: No IRQ available for PCI Interrupt Link [LNKD]. Try pci=noacpi or acpi=off

2016-09-29 Thread okaya
On 2016-09-29 05:10, Ondrej Zary wrote: On Thursday 29 September 2016, Sinan Kaya wrote: On 9/28/2016 3:23 PM, Ondrej Zary wrote: > On Wednesday 28 September 2016 20:22:40 Sinan Kaya wrote: >> On 9/28/2016 1:02 PM, Ondrej Zary wrote: Thanks, It sounds like you have more than one machine

Re: [PATCH] dmaengine: qcom_hidma: release the descriptor before the callback

2016-08-19 Thread okaya
On 2016-08-19 01:52, Vinod Koul wrote: On Thu, Aug 18, 2016 at 11:48:52PM -0400, Sinan Kaya wrote: On 8/18/2016 11:42 PM, Vinod Koul wrote: > On Thu, Aug 18, 2016 at 11:26:28PM -0400, Sinan Kaya wrote: >> On 8/18/2016 10:48 PM, Vinod Koul wrote: Keep a size limited list with error cookies

Re: [PATCH] dmaengine: qcom_hidma: release the descriptor before the callback

2016-08-08 Thread okaya
On 2016-08-08 04:51, Vinod Koul wrote: This patch is needed to fix a race condition as the commit message describes. The callback is called before returning the descriptor back to free pool. If the client calls free resources, the descriptor that was not returned to free pool gets lost due

Re: [PATCH 10/10] dmaengine: qcom_hidma: add MSI support for interrupts

2016-08-08 Thread okaya
On 2016-08-08 04:14, Vinod Koul wrote: On Thu, Aug 04, 2016 at 09:59:43AM -0400, Sinan Kaya wrote: On 8/4/2016 8:46 AM, Vinod Koul wrote: >> > Yes, I do have a new device ID for platforms with MSI capability. >> > >> > Which new binding are you referring to? > If you have "QCOM8062" why do you

Re: [PATCH V10 4/9] vfio: platform: add support for ACPI probe

2016-07-18 Thread okaya
On 2016-07-18 20:00, Alex Williamson wrote: On Mon, 18 Jul 2016 19:09:22 -0400 Sinan Kaya wrote: The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the

Re: [GIT PULL] ACPI fixes for v4.7-rc7

2016-07-10 Thread okaya
On 2016-07-10 14:00, Thorsten Leemhuis wrote: Hi Rafael! On 08.07.2016 01:43, Rafael J. Wysocki wrote: Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.7-rc7 to receive ACPI fixes for v4.7-rc7 with top-most commit […] All of these fix recent

Re: kernel-4.7 bug in Intel sound and/or ACPI

2016-06-30 Thread okaya
On 2016-06-30 05:30, Wim Osterholt wrote: On Wed, Jun 29, 2016 at 04:34:14AM -0400, Sinan Kaya wrote: > I posted this [PATCH V2 0/4] ACPI,PCI,IRQ: correct ISA penalty calculation Can you test this and give me a tested-by? Kernel-4.7-rc5 plus this patch works like a charm on my Inspiron

Re: kernel-4.7 bug in Intel sound and/or ACPI

2016-06-27 Thread okaya
On 2016-06-27 16:04, Wim Osterholt wrote: On Mon, Jun 27, 2016 at 04:22:18AM -0400, ok...@codeaurora.org wrote: > However, an earlier try on my Inspiron 510m did not work. > I'll do a clean retry later today, just to make sure. Ok, let me know. I can post a clean patch series. I was trying to

Re: kernel-4.7 bug in Intel sound and/or ACPI

2016-06-27 Thread okaya
On 2016-06-27 02:27, Wim Osterholt wrote: On Sat, Jun 25, 2016 at 04:51:03AM -0400, ok...@codeaurora.org wrote: On 2016-06-24 21:39, Wim Osterholt wrote: Please apply the patches on top of clean 4.7-rc4 tree and apply them in order with git am 0001... git am 0002... It doesn't work that

Re: kernel-4.7 bug in Intel sound and/or ACPI

2016-06-25 Thread okaya
On 2016-06-24 21:39, Wim Osterholt wrote: On Fri, Jun 24, 2016 at 02:09:15AM -0400, Sinan Kaya wrote: Can you give it a try? Whell, I tried to no avail. Wether it is on 4.6 or 4.7, with or without your previous patch, I keep getting rejected hunks. For example, here the line to be deleted

Re: kernel-4.7 bug in Intel sound and/or ACPI

2016-06-22 Thread okaya
On 2016-06-21 18:13, Wim Osterholt wrote: On Tue, Jun 21, 2016 at 09:40:10AM -0400, Sinan Kaya wrote: Thanks, It was a guess with no proof. Let's undo the change above and start adding some print statements to collect data from your system. Can you add this to the end of

RE: [RFC PATCH V2 1/2] ACPI/PCI: Match PCI config space accessors against platfrom specific ECAM quirks

2016-06-13 Thread okaya
On 2016-06-13 10:29, Gabriele Paoloni wrote: Hi Sinan -Original Message- From: Sinan Kaya [mailto:ok...@codeaurora.org] Sent: 13 June 2016 15:03 To: Gabriele Paoloni; liudongdong (C); helg...@kernel.org; a...@arndb.de; will.dea...@arm.com; catalin.mari...@arm.com; raf...@kernel.org;

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

2016-04-27 Thread okaya
On 2016-04-27 04:47, Marc Zyngier wrote: On 27/04/16 09:15, Vinod Koul wrote: On Tue, Apr 26, 2016 at 12:55:18PM -0400, Sinan Kaya wrote: On 4/26/2016 12:25 PM, Vinod Koul wrote: On Tue, Apr 26, 2016 at 08:08:16AM -0400, ok...@codeaurora.org wrote: On 2016-04-25 23:30, Vinod Koul wrote: On

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

2016-04-27 Thread okaya
On 2016-04-27 04:15, Vinod Koul wrote: On Tue, Apr 26, 2016 at 12:55:18PM -0400, Sinan Kaya wrote: On 4/26/2016 12:25 PM, Vinod Koul wrote: > On Tue, Apr 26, 2016 at 08:08:16AM -0400, ok...@codeaurora.org wrote: >> On 2016-04-25 23:30, Vinod Koul wrote: >>> On Mon, Apr 11, 2016 at 10:21:12AM

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

2016-04-26 Thread okaya
On 2016-04-25 23:30, Vinod Koul wrote: On Mon, Apr 11, 2016 at 10:21:12AM -0400, Sinan Kaya wrote: +static int hidma_chan_stats(struct seq_file *s, void *unused) +{ + struct hidma_chan *mchan = s->private; + struct hidma_desc *mdesc; + struct hidma_dev *dmadev =

Re: [PATCH V2] net: ethernet: mellanox: correct page conversion

2016-04-18 Thread okaya
On 2016-04-18 08:12, Christoph Hellwig wrote: On Sat, Apr 16, 2016 at 06:23:32PM -0400, Sinan Kaya wrote: Current code is assuming that the address returned by dma_alloc_coherent is a logical address. This is not true on ARM/ARM64 systems. Can you explain what you mean with a 'logical

Re: [PATCH V2] net: ethernet: mellanox: correct page conversion

2016-04-17 Thread okaya
On 2016-04-18 00:00, David Miller wrote: From: Sinan Kaya Date: Sat, 16 Apr 2016 18:23:32 -0400 Current code is assuming that the address returned by dma_alloc_coherent is a logical address. This is not true on ARM/ARM64 systems. This patch replaces dma_alloc_coherent

Re: [PATCH V4 4/7] ARM64, ACPI, PCI: I/O Remapping Table (IORT) initial support.

2016-04-14 Thread okaya
On 2016-04-14 03:36, Marc Zyngier wrote: On 14/04/16 08:20, Tomasz Nowicki wrote: On 13.04.2016 23:18, Sinan Kaya wrote: On 4/13/2016 11:52 AM, Marc Zyngier wrote: Sure. Please see: http://infocenter.arm.com/help/topic/com.arm.doc.den0049a/DEN0049A_IO_Remapping_Table.pdf 3.1.1.5 PCI root

Re: [PATCH V3 1/3] vfio, platform: add support for ACPI while detecting the reset driver

2016-03-29 Thread okaya
On 2016-03-29 07:25, Arnd Bergmann wrote: On Tuesday 29 March 2016 06:59:15 ok...@codeaurora.org wrote: On 2016-03-29 05:25, Arnd Bergmann wrote: > On Monday 28 March 2016 09:35:22 Sinan Kaya wrote: >> The code is using the compatible DT string to associate a reset driver >> with >> the actual

Re: [PATCH V3 1/3] vfio, platform: add support for ACPI while detecting the reset driver

2016-03-29 Thread okaya
On 2016-03-29 05:25, Arnd Bergmann wrote: On Monday 28 March 2016 09:35:22 Sinan Kaya wrote: The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the unique identifier for a

Re: [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single

2016-03-19 Thread okaya
On 2016-03-17 18:54, Russell King - ARM Linux wrote: On Thu, Mar 17, 2016 at 06:02:15PM -0400, Sinan Kaya wrote: Getting ready to remove dma_to_phys API. Drivers should not be using this API for DMA operations. Instead, they should go through the dma_map or dma_alloc APIs. Signed-off-by: Sinan

Re: [PATCH V14 5/9] dma: qcom_hidma: implement lower level hardware interface

2016-03-10 Thread Okaya
> On Thu, Feb 04, 2016 at 11:34:36PM -0500, Sinan Kaya wrote: > >> + >> +#define EVRE_SIZE 16 /* each EVRE is 16 bytes */ >> + >> +#define TRCA_CTRLSTS_OFFSET 0x000 >> +#define TRCA_RING_LOW_OFFSET0x008 >> +#define TRCA_RING_HIGH_OFFSET

Re: [PATCH V10 7/7] dma: qcom_hidma: add support for object hierarchy

2015-12-21 Thread Okaya
> Hi Sinan, > > [auto build test ERROR on v4.4-rc5] > [also build test ERROR on next-20151218] > > url: > https://github.com/0day-ci/linux/commits/Sinan-Kaya/dma-add-Qualcomm-Technologies-HIDMA-driver/20151218-010637 > config: sparc64-allmodconfig (attached as .config) > reproduce: > wget

Re: [PATCH V10 2/7] dma: hidma: Add Device Tree support

2015-12-21 Thread Okaya
> On Thu, Dec 17, 2015 at 12:01:17PM -0500, Sinan Kaya wrote: >> Add documentation for the Qualcomm Technologies HIDMA driver. >> >> Signed-off-by: Sinan Kaya >> --- >> .../devicetree/bindings/dma/qcom_hidma_mgmt.txt| 79 >> ++ >> 1 file changed, 79

Re: [PATCH V2 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

2015-12-21 Thread Okaya
> On Monday 21 December 2015, Tomasz Nowicki wrote: >> On 21.12.2015 13:10, Lorenzo Pieralisi wrote: >> > On Fri, Dec 18, 2015 at 06:56:39PM +, ok...@codeaurora.org wrote: > >> >> I have multiple root ports with the same IO port configuration in the >> >> current ACPI table. >> >> >> >> Root

Re: [PATCH V2 00/23] MMCONFIG refactoring and support for ARM64 PCI hostbridge init based on ACPI

2015-12-18 Thread okaya
> On 17.12.2015 22:24, Sinan Kaya wrote: >> Hi Tomasz, >> >> On 12/16/2015 10:16 AM, Tomasz Nowicki wrote: >>> From the functionality point of view this series might be split into >>> the >>> following logic parts: >>> 1. Make MMCONFIG code arch-agnostic which allows all architectures to >>>

Re: [PATCH V6 2/3] dma: add Qualcomm Technologies HIDMA management driver

2015-11-22 Thread okaya
> On Sun, Nov 22, 2015 at 6:37 PM, Sinan Kaya wrote: >> The Qualcomm Technologies HIDMA device has been designed >> to support virtualization technology. The driver has been >> divided into two to follow the hardware design. >> >> 1. HIDMA Management driver >> 2. HIDMA

Re: [PATCH V2 2/3] dmaselftest: add memcpy selftest support functions

2015-11-13 Thread okaya
>> >> I looked at this. IMO, merging selftest code and dmatest code is not >> a good idea. >> >> Dmatest code has been well written and structured so that multiple >> DMA capabilities (XOR, PQ, MEMCPY) can be tested with the same code. >> >> It supports threads and user space interaction. >> >>

Re: [PATCH] acpi: add support for extended IRQ to PCI link

2015-11-12 Thread okaya
> On Thu, Nov 12, 2015 at 5:04 PM, Sinan Kaya wrote: >> On 11/12/2015 4:56 AM, Andy Shevchenko wrote: >>> On Thu, Nov 12, 2015 at 8:14 AM, Sinan Kaya >>> wrote: - if (acpi_irq_balance || !link->irq.active) { + if