linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vaishnav M A <vaishnav@beagleboard.org>
To: johan@kernel.org
Cc: ribalda@kernel.org, robh@kernel.org, gregkh@linuxfoundation.org,
	jirislaby@kernel.org, masahiroy@kernel.org,
	andriy.shevchenko@linux.intel.com, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, linux-kbuild@vger.kernel.org,
	jkridner@beagleboard.org, drew@beagleboard.org,
	robertcnelson@beagleboard.org, vaishnav@beagleboard.org
Subject: [RFC PATCH 0/5] Add serdev_device_id for platform instantiation
Date: Mon, 26 Oct 2020 23:27:13 +0530	[thread overview]
Message-ID: <20201026175718.965773-1-vaishnav@beagleboard.org> (raw)

This patch series aims to add serdev_device_id to the serdev drivers
so as to support platform instantiation of a serdev device.The first
two patches adding the serdev_device_id has already been once submitted
by Ricardo Ribalda Delgado(in CC) here:
https://lore.kernel.org/lkml/20180611115240.32606-1-ricardo.ribalda@gmail.com/

The problem currently trying to solved is bit different from dynamically
loading/removing serdev devices as addressed in the original patch series,
the aim now is to attach a serdev driver once to a device that is not a part of
the device tree or the ACPI table, Eg. a device on a greybus created gbphy uart.

The patches were tested with a set of uBlox GNSS Receiver Clicks on a PocketBeagle.
The serdev_device_id table is exported only for a single driver(drivers/gnss/ubx.c)
for reference.

Ricardo Ribalda (2):
  serdev: Add serdev_device_id
  file2alias: Support for serdev devices

Vaishnav M A (3):
  serdev: add of_ helper to get serdev controller
  gnss: ubx add MODULE_DEVICE_TABLE(serdev)
  gnss: change of_property_read to device_property_read

 drivers/gnss/serial.c             |  3 +-
 drivers/gnss/ubx.c                |  9 +++++
 drivers/tty/serdev/core.c         | 58 +++++++++++++++++++++++++++----
 include/linux/mod_devicetable.h   | 10 ++++++
 include/linux/serdev.h            |  5 +++
 scripts/mod/devicetable-offsets.c |  3 ++
 scripts/mod/file2alias.c          | 10 ++++++
 7 files changed, 90 insertions(+), 8 deletions(-)

-- 
2.25.1


             reply	other threads:[~2020-10-26 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 17:57 Vaishnav M A [this message]
2020-10-26 17:57 ` [RFC PATCH 1/5] serdev: Add serdev_device_id Vaishnav M A
2020-10-26 17:57 ` [RFC PATCH 2/5] file2alias: Support for serdev devices Vaishnav M A
2020-10-26 17:57 ` [RFC PATCH 3/5] serdev: add of_ helper to get serdev controller Vaishnav M A
2020-10-26 17:57 ` [RFC PATCH 4/5] gnss: ubx add MODULE_DEVICE_TABLE(serdev) Vaishnav M A
2020-10-26 17:57 ` [RFC PATCH 5/5] gnss: change of_property_read to device_property_read Vaishnav M A

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201026175718.965773-1-vaishnav@beagleboard.org \
    --to=vaishnav@beagleboard.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=drew@beagleboard.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=jkridner@beagleboard.org \
    --cc=johan@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ribalda@kernel.org \
    --cc=robertcnelson@beagleboard.org \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).